[
http://jira.codehaus.org/browse/MDEPLOY-77?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=147770#action_147770
]
Carlo de Wolf commented on MDEPLOY-77:
--------------------------------------
To clarify:
Suppose you have the following dependency chain: A -> B -> C
Now if you deploy a snapshot of C which passes all unit tests, but for some
reason B can't be deployed because of unit test failures then A-SNAPSHOT
becomes useless for other projects. Anybody using that one will end up with a
'broken' C-SNAPSHOT.
Instead the dependency chain should be: A-1 -> B-1 -> C-1
Then it becomes: A-1 -> B-1 -> C-1, B-2 -> C-2 (where B-2 / SNAPSHOT fails to
deploy)
Now A-1 / SNAPSHOT still forms a latest stable snapshot chain.
> 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
