Parent pom 4.43.1 message from validate?

[Mark Waite]

Since the upgrade from pom 4.42 to 4.43.1, the plugins that I maintain are reporting a new series of warning messages from the maven `validate` goal.  Example plugins that show the message include https://ci.jenkins.io/job/Plugins/job/priority-sorter-plugin/job/master/121/console and https://ci.jenkins.io/job/Plugins/job/implied-labels-plugin/job/master/44/console

The message is reported on each of the plugins that has upgraded to pom 4.43.1.  Is there a setting that I should configure to avoid those warning messages?

The message is:

[WARNING] Missing:
----------
1) org.jenkins-ci.main:jenkins-test-harness:jar:1802.v9de0d87365d2

  Try downloading the file manually from the project website.

  Then, install it using the command:
      mvn install:install-file -DgroupId=org.jenkins-ci.main -DartifactId=jenkins-test-harness -Dversion=1802.v9de0d87365d2 -Dpackaging=jar -Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file there:
      mvn deploy:deploy-file -DgroupId=org.jenkins-ci.main -DartifactId=jenkins-test-harness -Dversion=1802.v9de0d87365d2 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency:
        1) org.jenkins-ci.main:jenkins-test-harness:jar:1802.v9de0d87365d2

----------
1 required artifact is missing.

for artifact:
  org.jenkins-ci.main:jenkins-test-harness:jar:1802.v9de0d87365d2

from the specified remote repositories:
  central (https://repo.maven.apache.org/maven2, releases=true, snapshots=false)
Path to dependency:
        1) org.jenkins-ci.main:jenkins-test-harness:jar:1802.v9de0d87365d2

[Jesse Glick]

On Sat, Jul 16, 2022 at 8:09 AM Mark Waite <mark.ea...@gmail.com> wrote:

for artifact:
  org.jenkins-ci.main:jenkins-test-harness:jar:1802.v9de0d87365d2

from the specified remote repositories:
  central (https://repo.maven.apache.org/maven2, releases=true, snapshots=false)

It is of course not in Central, it is in the Jenkins Artifactory. Which the POM for at least `priority-sorter` seems to correctly declare. Maybe your `~/.m2/settings.xml` declares a mirror which is not functioning correctly? Try

<mirrorOf>*,!repo.jenkins-ci.org,!incrementals</mirrorOf>

[Mark Waite]

On Tuesday, July 19, 2022 at 7:47:48 AM UTC-6 Jesse Glick wrote:

On Sat, Jul 16, 2022 at 8:09 AM Mark Waite wrote:

for artifact:
  org.jenkins-ci.main:jenkins-test-harness:jar:1802.v9de0d87365d2

from the specified remote repositories:
  central (https://repo.maven.apache.org/maven2, releases=true, snapshots=false)

It is of course not in Central, it is in the Jenkins Artifactory. Which the POM for at least `priority-sorter` seems to correctly declare. Maybe your `~/.m2/settings.xml` declares a mirror which is not functioning correctly? Try

<mirrorOf>*,!repo.jenkins-ci.org,!incrementals</mirrorOf>

Thanks.  I assume that the mirror configuration on ci.jenkins.io is also incorrect, since it reports the same message in https://ci.jenkins.io/job/Plugins/job/priority-sorter-plugin/job/master/lastBuild/console ? 

[Basil Crow]

This appears to be a regression in MojoHaus Extra Enforcer Rules introduced in mojohaus/extra-enforcer-rules#220 and released in 1.6.0. Refer to the Extra Enforcer Rules - Issue Management page for instructions on how to report an issue to the MojoHaus Extra Enforcer Rules developers.

[Jesse Glick]

I did not see any such message in `priority-sorter-plugin`. Is there a way to reproduce?

[Mark Waite]

On Tuesday, July 19, 2022 at 11:10:22 AM UTC-6 Jesse Glick wrote:

I did not see any such message in `priority-sorter-plugin`. Is there a way to reproduce?

Thanks for sharing that you don't see that message.  Your earlier comment about my settings.xml having an incorrect mirror definition seems to be the key to the difference in what you see and what I see.

I see the message with my previous mirror definition:

  <mirrors>
    <mirror>
      <id>repo.jenkins-ci.org</id>
      <url>https://repo.jenkins-ci.org/public/</url>
      <mirrorOf>m.g.o-public</mirrorOf> -->
    </mirror>
  </mirrors>

I don't see the message with the corrected mirror definition:

  <mirrors>
    <mirror>
      <id>repo.jenkins-ci.org</id>
      <url>https://repo.jenkins-ci.org/public/</url>
      <mirrorOf>*,!repo.jenkins-ci.org,!incrementals</mirrorOf>
    </mirror>
  </mirrors>

I'll correct my mirror definition and see if I can find the location on ci.jenkins.io to correct its mirror definition as well.

Thanks again!

Mark Waite

[Basil Crow]

I do not have any mirrors defined in my ~/.m2/settings.xml file but I see the problem in Text Finder (Maven 3.8.6, Java 17) with mojohaus/extra-enforcer-rules#220 and I do not see the problem with that commit reverted.

[Ivan Fernandez Calvo]

I updated SAML, SSH build Agents, and trilead-api to that Jenkins of the parent pom without issues, these plugins are in BOM version 1478.v81d3dc4f9a_43 I have noticed those plugins use 1500.ve4d05cd32975 that is the latest
, maybe is related.

https://github.com/jenkinsci/saml-plugin/blob/main/pom.xml#L28

https://github.com/jenkinsci/ssh-slaves-plugin/blob/main/pom.xml#L8

https://github.com/jenkinsci/trilead-api-plugin/blob/main/pom.xml#L8

[Mark Waite]

I've made a best effort to submit the issue to the extras enforcer project based on the research that Basil did.

https://github.com/mojohaus/extra-enforcer-rules/issues/225