[
https://jira.codehaus.org/browse/MRELEASE-882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jörg Schaible closed MRELEASE-882.
----------------------------------
Resolution: Not A Bug
Actually it was a very unfortunate sequence of failures. I wanted to release
our master POM in new version 274, but I typed version 247, with the effect
that the tag got nested in subversion "../tags/v_247/v_247". The checkout then
provided the real version 247 and there were the versions declared I've seen.
Even worse, I did not recognize the real culprit, so I downgraded the release
plugin, dropped the tag in subversion (../tags/v_247) and did the release
again. Since release:prepare could now create the tag at the correct position,
performing the release worked ... unfortunately. I try to clean up currently
the mess I've created ;-)
> [regression] Perform fails because usage of site plugin with wrong version
> --------------------------------------------------------------------------
>
> Key: MRELEASE-882
> URL: https://jira.codehaus.org/browse/MRELEASE-882
> Project: Maven Release Plugin
> Issue Type: Bug
> Components: perform
> Affects Versions: 2.5
> Reporter: Jörg Schaible
>
> We use M322 and define the version 3.4 for the site plugin in our POM using a
> version property. The output of help:effective-pom verifies that the
> site-plugin is declared using version 3.4. However, release:perform fails
> with (snippet):
> {noformat}
> [INFO] --- maven-release-plugin:2.5:perform (default-cli) @ master ---
> [INFO] Checking out the project to perform the release ...
> ...
> [INFO] [INFO] --- maven-site-plugin:3.0-beta-3:site (default-site) @ master
> ---
> [INFO] [WARNING] Error injecting:
> org.apache.maven.plugins.site.DefaultMavenReportExecutor
> [INFO] java.lang.NoClassDefFoundError:
> org/sonatype/aether/graph/DependencyFilter
> [INFO] at java.lang.Class.getDeclaredConstructors0(Native Method)
> [INFO] at java.lang.Class.privateGetDeclaredConstructors(Class.java:2532)
> {noformat}
> Obviously the release:perform goal of the release plugin in version 2.5 uses
> now version 3.0-beta-3 of the site plugin with is incompatible.
> When we go back to version 2.4.2 of the release plugin, it uses the correct
> (declared) version of the site plugin and the release is performed
> successfully.
> Comparing the used plugin versions during release:perform, it is not only the
> version of the site plugin that is wrong. It seems that any declared plugin
> version is simply ignored with release plugin version 2.5.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
