Guidance on whether/where to file issues for build warnings

[Tim Van Holder]

Hi,

I'm currently encountering a few warnings when building.

They may be only warnings, but a) warnings irk me, and b) they don't seem to be caused by anything I am doing myself, which makes them extra irksome.

During build I get:

[WARNING] The artifact xml-apis:xml-apis:jar:2.0.2 has been relocated to xml-apis:xml-apis:jar:1.0.b2
[INFO]
[INFO] -------------------< io.jenkins.plugins:dotnet-sdk >--------------------
[INFO] Building .NET SDK Support 1.3.2-SNAPSHOT
[INFO] --------------------------------[ hpi ]---------------------------------
[WARNING] The artifact xerces:xerces:jar:2.2.1 has been relocated to xerces:xercesImpl:jar:2.2.1

I don't have any direct references to either of these. Is this a bug in the BOM?

Update: as I was composing this, I was also updating my build software (JDK 8/11/17, Maven, Groovy) just to make sure it wasn't a bug in any of those.

And these warnings went away when using Maven 3.8.5 instead of 3.8.3.

So that's half the problem already solved.

When generating JavaDoc using "mvn javadoc:aggregate-jar", I get

[WARNING] warning: unknown enum constant When.MAYBE
[WARNING] reason: class file for javax.annotation.meta.When not found
[WARNING] warning: unknown enum constant When.ALWAYS
[WARNING] warning: unknown enum constant When.UNKNOWN

I don't use this enum at all. In fact, the only reference to javax.annotation.meta.When I can find, is in the 3 different versions of the "jsr305" library in my local .m2/repository (part of findbugs, apparently). Also not I library I'm directly referencing, so I'm slightly confused as to why the javadoc processing cares.

Is this a case of an incomplete classpath when running javadoc? I don't set anything up for that specifically; my pom.xml just has

  <build>
    <plugins>
      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-javadoc-plugin</artifactId>
        <configuration>
          <doclint>all</doclint>
        </configuration>
      </plugin>
    </plugins>
  </build>

Am I missing required configuration, or does that make it something that's set up incorrectly in the plugin parent, or possibly in the BOM?

[Jesse Glick]

On Fri, May 13, 2022 at 5:50 PM Tim Van Holder <tim.va...@gmail.com> wrote:

I don't have any direct references to either of these. Is this a bug in the BOM?

Or the parent POM, or something. If you manage to track down the root cause, please file a PR to fix it.

And these warnings went away when using Maven 3.8.5 instead of 3.8.3.

Do not use 3.8.5; it is known to be broken. Use 3.8.4.