[
https://issues.jenkins-ci.org/browse/JENKINS-13637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163281#comment-163281
]
jglick commented on JENKINS-13637:
----------------------------------
Activating the Jenkins repos by default, which would affect _any_ Maven
projects, does not seem like a reasonable workaround; passing {{\-Pjenkins}}
during {{release:prepare}} would be an unpleasant but unacceptable workaround
if that sufficed. A proper fix would be in {{plugin-*.pom}} to declare the
{{pluginRepository}} it needs (or avoid using {{maven-hpi-plugin}} if it does
not), so that the release plugin works without special configuration.
> Cannot release using M3
> -----------------------
>
> Key: JENKINS-13637
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13637
> Project: Jenkins
> Issue Type: Bug
> Components: plugin
> Environment: Ubuntu, JDK 6
> Reporter: jglick
> Labels: maven, release-plugin
>
> Given the {{mercurial}} plugin with parent
> {{org.jenkins-ci.plugins:plugin:1.400}}, but also reproducible with
> {{1.461}}, Maven 3 {{mvn -B release:prepare}} fails with
> {code}
> [INFO] Checking dependencies and plugins for snapshots ...
> [INFO] Transforming 'Jenkins Mercurial plugin'...
> Downloading:
> <CENTRAL_MIRROR>/org/jenkins-ci/tools/maven-hpi-plugin/1.74/maven-hpi-plugin-1.74.pom
> [WARNING] The POM for org.jenkins-ci.tools:maven-hpi-plugin:jar:1.74 is
> missing, no dependency information available
> Downloading:
> <CENTRAL_MIRROR>/org/jenkins-ci/tools/maven-hpi-plugin/1.74/maven-hpi-plugin-1.74.jar
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 5.310s
> [INFO] Finished at: Fri Apr 27 19:30:03 EDT 2012
> [INFO] Final Memory: 10M/164M
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-release-plugin:2.2.1:prepare (default-cli) on
> project mercurial: Execution default-cli of goal
> org.apache.maven.plugins:maven-release-plugin:2.2.1:prepare failed: Failed to
> build parent project for org.jenkins-ci.plugins:mercurial:hpi:1.39-SNAPSHOT:
> Some problems were encountered while processing the POMs:
> [ERROR] [ERROR] Unresolveable build extension: Plugin
> org.jenkins-ci.tools:maven-hpi-plugin:1.74 or one of its dependencies could
> not be resolved: Could not find artifact
> org.jenkins-ci.tools:maven-hpi-plugin:jar:1.74 in central (<CENTRAL_MIRROR>/)
> @: 1 problem was encountered while building the effective model for
> org.jenkins-ci.plugins:plugin:1.461
> [ERROR] [ERROR] Unresolveable build extension: Plugin
> org.jenkins-ci.tools:maven-hpi-plugin:1.74 or one of its dependencies could
> not be resolved: Could not find artifact
> org.jenkins-ci.tools:maven-hpi-plugin:jar:1.74 in central (<CENTRAL_MIRROR>/)
> @
> {code}
> Indeed I think the error message is correct: {{plugin-1.400.pom}} (or again
> {{plugin-1.461.pom}}) refers to {{maven-hpi-plugin}} yet does not declare any
> {{<pluginRepository>}} in which it might be found. (Nor does its own parent.)
> Maven 2 succeeds in this case; apparently it does not care where the plugin
> came from. But Maven 3 as described in
> https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html#Maven3.xCompatibilityNotes-ResolutionfromLocalRepository
> does care.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
