Maven 2.x and 3.x Deploy Plugin

Add new option to resolve snapshot dependencies when deploying

Details

  • Type: New Feature New Feature
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Won't Fix
  • Affects Version/s: None
  • Fix Version/s: None
  • Component/s: None
  • Labels:
    None
  • Number of attachments :
    0

Description

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.

Issue Links

is related to

New Feature - A new feature of the product, which has yet to be developed. MVERSIONS-21 Add mojo to lock snapshots to timestamp version

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Carlo de Wolf added a comment -

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.

Show
Carlo de Wolf added a comment - 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.
Hide
Permalink
Paul Gier added a comment -

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.

Show
Paul Gier added a comment - 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.

People

  • Assignee:
    Unassigned
    Reporter:
    Paul Gier
Vote (1)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved: