`'distributionManagement.status' must not be specified.`

[jglick]

@MarkEWaite found in git-client-plugin among others a minor regression introduced acc. git bisect by @basil’s #310:: a nonfatal message

[ERROR] 'distributionManagement.status' must not be specified. @ line 166, column 13

I have no idea what it means (cannot find anything interesting at line 166 in either the plugin’s POM or plugin-pom). Maybe coming from some unnamed dependency.

[MarkEWaite]

One difference between the 3 plugins where I see the issue and the 5 plugins where I do not see the issue is that the 3 with the problem all require a Jenkins 2.289.1 or older. The plugins where I do not see the issue all require at least Jenkins 2.303.1

The plugins that show the issue:

• https://github.com/jenkinsci/git-client-plugin
• https://github.com/jenkinsci/git-plugin
• https://github.com/jenkinsci/priority-sorter-plugin

The plugins that don't show the issue:

• https://github.com/jenkinsci/elastic-axis-plugin
• https://github.com/jenkinsci/nodelabelparameter-plugin
• https://github.com/jenkinsci/platformlabeler-plugin
• https://github.com/jenkinsci/schedule-build-plugin
• https://github.com/jenkinsci/testng-plugin-plugin

The message no longer appears in the git client plugin when I update the parent pom to 2.319.3. I think that suggests the best course of action is for plugins to update their minimum required Jenkins version to at least the recommended minimum version.

[jglick]

Interesting @MarkEWaite. If you had the time to spare, you could bisect on jenkins.version to find the weekly release (and then, if necessary, the commit) which made the message go away.

[basil]

I hit this breakpoint:

validateEffectiveModel:457, DefaultModelValidator (org.apache.maven.model.validation)
build:564, DefaultModelBuilder (org.apache.maven.model.building)
build:454, DefaultModelBuilder (org.apache.maven.model.building)
build:267, DefaultModelBuilder (org.apache.maven.model.building)
build:173, DefaultProjectBuilder (org.apache.maven.project)
build:342, DefaultProjectBuilder (org.apache.maven.project)
build:299, DefaultProjectBuilder (org.apache.maven.project)
resolvePom:56, MavenArtifact (org.jenkinsci.maven.plugins.hpi)
getResolvedType:250, MavenArtifact (org.jenkinsci.maven.plugins.hpi)
isPlugin:63, MavenArtifact (org.jenkinsci.maven.plugins.hpi)
isPluginBestEffort:73, MavenArtifact (org.jenkinsci.maven.plugins.hpi)
execute:29, ValidateHpiMojo (org.jenkinsci.maven.plugins.hpi)
executeMojo:137, DefaultBuildPluginManager (org.apache.maven.plugin)
doExecute:301, MojoExecutor (org.apache.maven.lifecycle.internal)
execute:211, MojoExecutor (org.apache.maven.lifecycle.internal)
execute:165, MojoExecutor (org.apache.maven.lifecycle.internal)
execute:157, MojoExecutor (org.apache.maven.lifecycle.internal)
buildProject:121, LifecycleModuleBuilder (org.apache.maven.lifecycle.internal)
buildProject:81, LifecycleModuleBuilder (org.apache.maven.lifecycle.internal)
build:56, SingleThreadedBuilder (org.apache.maven.lifecycle.internal.builder.singlethreaded)
execute:127, LifecycleStarter (org.apache.maven.lifecycle.internal)
doExecute:294, DefaultMaven (org.apache.maven)
doExecute:192, DefaultMaven (org.apache.maven)
execute:105, DefaultMaven (org.apache.maven)
execute:960, MavenCli (org.apache.maven.cli)
doMain:293, MavenCli (org.apache.maven.cli)
main:196, MavenCli (org.apache.maven.cli)
invoke0:-1, NativeMethodAccessorImpl (jdk.internal.reflect)
invoke:77, NativeMethodAccessorImpl (jdk.internal.reflect)
invoke:43, DelegatingMethodAccessorImpl (jdk.internal.reflect)
invoke:568, Method (java.lang.reflect)
launchEnhanced:282, Launcher (org.codehaus.plexus.classworlds.launcher)
launch:225, Launcher (org.codehaus.plexus.classworlds.launcher)
mainWithExitCode:406, Launcher (org.codehaus.plexus.classworlds.launcher)
main:347, Launcher (org.codehaus.plexus.classworlds.launcher)

So the "[ERROR] 'distributionManagement.status' must not be specified. @ line 166, column 13" is coming from commons-discovery-0.4.pom which does indeed have this near line 166:

  <distributionManagement>
    <repository>
      <id>default</id>
      <name>Default Repository</name>
      <url>file:///www/jakarta.apache.org/builds/jakarta-commons/${pom.artifactId.substring(8)}/</url>
    </repository>
    <site>
      <id>default</id>
      <name>Default Site</name>
      <url>scp://people.apache.org//www/jakarta.apache.org/commons/${pom.artifactId.substring(8)}/</url>
    </site>
    <status>converted</status>
  </distributionManagement>

[jglick]

Do not recognize that artifact, but I guess it is something present in older cores which has since been either removed or upgraded to a version with a corrected POM? If so, then I suppose this should just be closed.

[basil]

The problematic dependency is pulled in via:

[INFO] +- org.jenkins-ci.main:jenkins-core:jar:2.289.1:provided
[…]
[INFO] |  +- org.kohsuke.stapler:stapler:jar:1.263:provided
[…]
[INFO] |  |  +- commons-discovery:commons-discovery:jar:0.4:provided

This was upgraded to 0.5 a year ago in jenkinsci/stapler#222, released in Stapler 1539.v2f05ce93882d, upgraded to in jenkinsci/jenkins#5549, and released in Jenkins 2.299.