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
