You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Robert Scholte (JIRA)" <ji...@codehaus.org> on 2012/02/28 18:42:02 UTC

[jira] (MRELEASE-333) allowTimestampedSnapshots is not applied to report plugins

     [ https://jira.codehaus.org/browse/MRELEASE-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Scholte closed MRELEASE-333.
-----------------------------------

    Resolution: Incomplete

No feedback from user, closing it as {{incomplete}}.
                
> allowTimestampedSnapshots is not applied to report plugins
> ----------------------------------------------------------
>
>                 Key: MRELEASE-333
>                 URL: https://jira.codehaus.org/browse/MRELEASE-333
>             Project: Maven 2.x Release Plugin
>          Issue Type: Bug
>          Components: prepare
>    Affects Versions: 2.0-beta-7
>         Environment: Any
>            Reporter: Kalle Korhonen
>         Attachments: pom.xml
>
>
> Related to already resolved MRELEASE-124. allowTimestampedSnapshots make it possible to force a release with uniquely versioned snapshots as dependencies, but the parameter has no effect on report snapshots dependencies. Looking at the code in the patch it seems the parameter is only applied to straight-up project dependencies. If you are forced to use reports that are only available as snapshots (currently e.g. the dashboard plugin), you are out of luck unless you deploy custom versions of the plugin in your internal repository or disable the reports for the release.

--
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