You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Stephen Connolly (JIRA)" <ji...@codehaus.org> on 2011/07/01 11:22:42 UTC

[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

     [ 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