You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Angel Ruiz (JIRA)" <ji...@codehaus.org> on 2009/04/23 06:34:44 UTC
[jira] Created: (MRELEASE-441) Bad pom generation when trying to
prepare release for a multimodule project with some timestamp snapshot
dependencies even using the parameter -DallowTimestampedSnapshots=true
Bad pom generation when trying to prepare release for a multimodule project with some timestamp snapshot dependencies even using the parameter -DallowTimestampedSnapshots=true
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: MRELEASE-441
URL: http://jira.codehaus.org/browse/MRELEASE-441
Project: Maven 2.x Release Plugin
Issue Type: Bug
Affects Versions: 2.0-beta-9
Environment: jdk 1.6
maven 2.1.0
Reporter: Angel Ruiz
Priority: Critical
I have a Maven2 multi-module project with 3 modules. There is one with a time-stamp snapshot dependency and other two that both have the same snapshot repository.
I execute the following command: mvn release:prepare -DallowTimestampedSnapshots=true -DdryRun=true and everything seems to be fine, but when I have a look to the pom.xml.tag file, I see that the first module still maintains the time-stamp snapshot dependencies, but the plugin has elminated the time-stamp from the dependency in the other two modules. I reckon that this must be a bug, so maybe the DallowTimestampedSnapshots parameter works for the first dependency and then it is lost or ignored when generating the new pom file for the other two modules with time-stamp dependencies.
Cheers.
--
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] Updated: (MRELEASE-441) Bad pom generation when trying to
prepare release for a multimodule project with some timestamp snapshot
dependencies even using the parameter -DallowTimestampedSnapshots=true
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Lundberg updated MRELEASE-441:
-------------------------------------
Component/s: prepare
> Bad pom generation when trying to prepare release for a multimodule project with some timestamp snapshot dependencies even using the parameter -DallowTimestampedSnapshots=true
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MRELEASE-441
> URL: http://jira.codehaus.org/browse/MRELEASE-441
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.0-beta-9
> Environment: jdk 1.6
> maven 2.1.0
> Reporter: Angel Ruiz
> Priority: Critical
>
> I have a Maven2 multi-module project with 3 modules. There is one with a time-stamp snapshot dependency and other two that both have the same snapshot repository.
> I execute the following command: mvn release:prepare -DallowTimestampedSnapshots=true -DdryRun=true and everything seems to be fine, but when I have a look to the pom.xml.tag file, I see that the first module still maintains the time-stamp snapshot dependencies, but the plugin has elminated the time-stamp from the dependency in the other two modules. I reckon that this must be a bug, so maybe the DallowTimestampedSnapshots parameter works for the first dependency and then it is lost or ignored when generating the new pom file for the other two modules with time-stamp dependencies.
> Cheers.
--
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-441) Bad pom generation when trying to prepare
release for a multimodule project with some timestamp snapshot dependencies
even using the parameter -DallowTimestampedSnapshots=true
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte closed MRELEASE-441.
-----------------------------------
Resolution: Not A Bug
Assignee: Robert Scholte
{{allowTimestampedSnapshots}} is *_not_* a commandline parameter, use {{-DignoreSnapshots=true}} instead. See MRELEASE-632 for further details.
> Bad pom generation when trying to prepare release for a multimodule project with some timestamp snapshot dependencies even using the parameter -DallowTimestampedSnapshots=true
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MRELEASE-441
> URL: https://jira.codehaus.org/browse/MRELEASE-441
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.0-beta-9
> Environment: jdk 1.6
> maven 2.1.0
> Reporter: Angel Ruiz
> Assignee: Robert Scholte
> Priority: Critical
> Labels: scrub-review-started
>
> I have a Maven2 multi-module project with 3 modules. There is one with a time-stamp snapshot dependency and other two that both have the same snapshot repository.
> I execute the following command: mvn release:prepare -DallowTimestampedSnapshots=true -DdryRun=true and everything seems to be fine, but when I have a look to the pom.xml.tag file, I see that the first module still maintains the time-stamp snapshot dependencies, but the plugin has elminated the time-stamp from the dependency in the other two modules. I reckon that this must be a bug, so maybe the DallowTimestampedSnapshots parameter works for the first dependency and then it is lost or ignored when generating the new pom file for the other two modules with time-stamp dependencies.
> Cheers.
--
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] Updated: (MRELEASE-441) Bad pom generation when trying to
prepare release for a multimodule project with some timestamp snapshot
dependencies even using the parameter -DallowTimestampedSnapshots=true
Posted by "Stephen Connolly (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stephen Connolly updated MRELEASE-441:
--------------------------------------
Labels: scrub-review-started (was: )
Do you think you could please provide a test case as it will help making developing a fix easier.
> Bad pom generation when trying to prepare release for a multimodule project with some timestamp snapshot dependencies even using the parameter -DallowTimestampedSnapshots=true
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MRELEASE-441
> URL: https://jira.codehaus.org/browse/MRELEASE-441
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.0-beta-9
> Environment: jdk 1.6
> maven 2.1.0
> Reporter: Angel Ruiz
> Priority: Critical
> Labels: scrub-review-started
>
> I have a Maven2 multi-module project with 3 modules. There is one with a time-stamp snapshot dependency and other two that both have the same snapshot repository.
> I execute the following command: mvn release:prepare -DallowTimestampedSnapshots=true -DdryRun=true and everything seems to be fine, but when I have a look to the pom.xml.tag file, I see that the first module still maintains the time-stamp snapshot dependencies, but the plugin has elminated the time-stamp from the dependency in the other two modules. I reckon that this must be a bug, so maybe the DallowTimestampedSnapshots parameter works for the first dependency and then it is lost or ignored when generating the new pom file for the other two modules with time-stamp dependencies.
> Cheers.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira