You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Paul Gier (JIRA)" <ji...@codehaus.org> on 2009/03/24 16:56:13 UTC
[jira] Closed: (MDEPLOY-77) Add new option to resolve snapshot
dependencies when deploying
[ http://jira.codehaus.org/browse/MDEPLOY-77?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Gier closed MDEPLOY-77.
----------------------------
Resolution: Won't Fix
The consensus seems to be that the deploy plugin should not have any responsibility related to modifying the pom. So MVERSIONS-21 should handle this use case instead. It can be run prior to deployment to lock down the snapshot versions.
> Add new option to resolve snapshot dependencies when deploying
> --------------------------------------------------------------
>
> Key: MDEPLOY-77
> URL: http://jira.codehaus.org/browse/MDEPLOY-77
> Project: Maven 2.x Deploy Plugin
> Issue Type: New Feature
> Reporter: Paul Gier
>
> It would be helpful in certain cases to tie a snapshot deployment to certain snapshot dependencies. For example, I have a dependency on project A version 1.0-SNAPSHOT. When my project is deployed, I would like this to be resolved to the specific snapshot used during the build. So something like (1.0-20080201.133452-3). This way I can see exactly which dependency build was used during the build of my project.
--
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