[
https://jira.codehaus.org/browse/MRELEASE-643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=300406#comment-300406
]
Robert Scholte edited comment on MRELEASE-643 at 6/5/12 11:07 AM:
------------------------------------------------------------------
This is not a {{maven-release-plugin}} bug, but a Maven-bug. Up to version
{{3.0.3}} the {{super-pom.xml}} contained a 2.x version of the
{{maven-site-plugin}}, which is incompatible with Maven3. This has been fix for
Maven-3.0.4
But... you shouldn't rely on the versions in the {{super-pom}}, because they
can be upgraded with every new release of Maven. It's a best practice to
include these plugins in your own pom with a locked version to keep the build
stable for ages.
was (Author: rfscholte):
This is not a ((maven-release-plugin}} bug, but a Maven-bug. Up to version
{{3.0.3}} the {{super-pom.xml}} contained a 2.x version of the
{{maven-site-plugin}}, which is incompatible with Maven3. This has been fix for
Maven-3.0.4
But... you shouldn't rely on the versions in the {{super-pom}}, because they
can be upgraded with every new release of Maven. It's a best practice to
include these plugins in your own pom with a locked version to keep the build
stable for ages.
> it wont use maven-site-plugin 3.0-beta-3 when used with Maven 3.0.2
> --------------------------------------------------------------------
>
> Key: MRELEASE-643
> URL: https://jira.codehaus.org/browse/MRELEASE-643
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: perform
> Affects Versions: 2.1
> Environment: Win 7 64-bit
> Maven 3.0.2
> Reporter: shane mills
> Assignee: Robert Scholte
>
> We use Maven as project management tool.
> For building releases we use maven-release-plugin.
> Up until a few days ago we used Maven 2.2.1 but unfortunately we recognized
> that for some reason when triggering "mvn release:prepare" on a project with
> local modifications it would just prepare the release without saying anything
> about it.
> We actually just recognized this issue a few days ago so I started to track
> down the problem with no result but the fact that with maven 3 it terminates
> just as expected. So instead of tracking down the maven 2.2.1 issue i started
> to check on maven 3 and if we could use it instead of maven 2.2.1.
> Actually everything works just fine except of the site-plugin. I found out
> that with maven 3.x you should use the site-plugin 3.x and so i tried to bend
> dependencies so that the release-plugin uses the site-plugin 3.0-beta-3
> instead of site-plugin 2.0.1, but it just wont do so.
> When triggering "mvn site:site" on the command line it works just fine, but
> when triggering "mvn release:prepare" and afterwards "mvn release:perform" it
> still uses the site-plugin 2.0.1 not as expected maven-site-plugin 3.0-beta-3.
> I am using maven 3.0.2 with maven-release-plugin 2.0.1
> We are looking forward to switching to maven 3.x but at first we need to be
> sure everything works at least as fine as with maven 2.2.1 :)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
