You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "shane mills (JIRA)" <ji...@codehaus.org> on 2011/02/04 15:36:22 UTC
[jira] Created: (MRELEASE-643) it wont use maven-site-plugin
3.0-beta-3 when used with Maven 3.0.2
it wont use maven-site-plugin 3.0-beta-3 when used with Maven 3.0.2
--------------------------------------------------------------------
Key: MRELEASE-643
URL: http://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
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 contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-643) it wont use maven-site-plugin 3.0-beta-3 when
used with Maven 3.0.2
Posted by "shane mills (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=300360#comment-300360 ]
shane mills commented on MRELEASE-643:
--------------------------------------
I am very sorry for not responding. I passed this issue to a colleague who tested it (afaik) successfully. I forgot all about this issue, sorry. I will ask this colleague whether I am right. I not so I will comment here once again.
> 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
[jira] (MRELEASE-643) it wont use maven-site-plugin 3.0-beta-3 when
used with Maven 3.0.2
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] (MRELEASE-643) it wont use maven-site-plugin 3.0-beta-3 when
used with Maven 3.0.2
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=292127#comment-292127 ]
Robert Scholte commented on MRELEASE-643:
-----------------------------------------
Maven-3.0.4 has been released, can you still reproduce this issue?
> 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
>
> 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
[jira] (MRELEASE-643) it wont use maven-site-plugin 3.0-beta-3 when
used with Maven 3.0.2
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte closed MRELEASE-643.
-----------------------------------
Resolution: Incomplete
Assignee: Robert Scholte
No feedback from user, closing it.
> 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
[jira] (MRELEASE-643) it wont use maven-site-plugin 3.0-beta-3 when
used with Maven 3.0.2
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte reopened MRELEASE-643:
-------------------------------------
> 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
[jira] (MRELEASE-643) it wont use maven-site-plugin 3.0-beta-3 when
used with Maven 3.0.2
Posted by "shane mills (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=300360#comment-300360 ]
shane mills edited comment on MRELEASE-643 at 6/5/12 1:38 AM:
--------------------------------------------------------------
I am very sorry for not responding. I passed this issue to a colleague who tested it (afaik) successfully. I forgot all about this issue, sorry. I will ask this colleague whether I am right. If not so I will comment here once again.
EDIT: Ok, as I remembered, everything works just great with 3.0.4:) Thank you for taking your time.
was (Author: etherid):
I am very sorry for not responding. I passed this issue to a colleague who tested it (afaik) successfully. I forgot all about this issue, sorry. I will ask this colleague whether I am right. If not so I will comment here once again.
> 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
[jira] (MRELEASE-643) it wont use maven-site-plugin 3.0-beta-3 when
used with Maven 3.0.2
Posted by "shane mills (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=300469#comment-300469 ]
shane mills commented on MRELEASE-643:
--------------------------------------
Of course you are right about including such plugins in our own pom and I believe that is what we do since we switched to Maven 3.
The time this Issue was created I tried Maven with some projekt we hadn't released for some time.
If I recall correctly I actually tried to define the site plugin inside the projects pom.
Anyways, it works just great and we allready upgraded almost all our projects to Maven 3.
> 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
[jira] (MRELEASE-643) it wont use maven-site-plugin 3.0-beta-3 when
used with Maven 3.0.2
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte closed MRELEASE-643.
-----------------------------------
Resolution: Not A Bug
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
[jira] (MRELEASE-643) it wont use maven-site-plugin 3.0-beta-3 when
used with Maven 3.0.2
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=288180#comment-288180 ]
Robert Scholte commented on MRELEASE-643:
-----------------------------------------
Looks related to MNG-5225, let's wait for Maven-3.0.4 and let's give it another try.
> 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
>
> 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
[jira] (MRELEASE-643) it wont use maven-site-plugin 3.0-beta-3 when
used with Maven 3.0.2
Posted by "shane mills (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=300360#comment-300360 ]
shane mills edited comment on MRELEASE-643 at 6/5/12 1:29 AM:
--------------------------------------------------------------
I am very sorry for not responding. I passed this issue to a colleague who tested it (afaik) successfully. I forgot all about this issue, sorry. I will ask this colleague whether I am right. If not so I will comment here once again.
was (Author: etherid):
I am very sorry for not responding. I passed this issue to a colleague who tested it (afaik) successfully. I forgot all about this issue, sorry. I will ask this colleague whether I am right. I not so I will comment here once again.
> 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