[
http://jira.codehaus.org/browse/MRELEASE-583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=236834#action_236834
]
Marcus Linke commented on MRELEASE-583:
---------------------------------------
Hello bret, in my oppinion this is not the correct default behaviour for the
next development version. If a snapshot dependency is used in a project this is
usually not an external dependency, isn't it? External dependencies are used as
releases normally. So I think snapshot dependencies are rather internal
dependencies (where release cycle of the dependency is under own control) in
the most cases.
Assuming this, the next development version of a project should point to the
latest development version of the dependency, at least for my use case ;)
Switching manually to the dependencies next development version is really
error-prone...
But maybe the concrete behavior should be configurable to reflect possible
different usecases?
> Better Snapshot Dependency Handling
> -----------------------------------
>
> Key: MRELEASE-583
> URL: http://jira.codehaus.org/browse/MRELEASE-583
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Components: prepare
> Affects Versions: 2.0
> Reporter: nicola sinapsi
> Assignee: Brett Porter
> Fix For: 2.1
>
> Attachments: better-snapshot-dependency.patch
>
>
> The plugin has a simple snapshot dependency resolution mechanism.
> When a snapshot dependency is found, it allows for setting it to release...
> but it does not allows to choice the release version to use:
> <code>
> Resolve Project Dependency Snapshots.: 'com.sinapsi.libs:sinapsi-commons' set
> to release? (yes/no) yes: : yes
> What is the next development version? (2.1.3-SNAPSHOT) 2.1.3-SNAPSHOT: :
> </code>
> in this case the versions are:
> current: 2.1.2-SNAPSHOT
> release: 2.1.2
> next: 2.1.3-SNAPSHOT
> The problem is that the only allowed development version is 2.1.3-SNAPSHOT
> (the value between the parentheses), hence the only allowed release version
> is 2.1.2.
> Notably, you cannot specify an OLDER relase (such as 2.1.1): this means you
> are forced to release the dependency (you cannot use an already released
> version).
> It would be better to ask for the release version to use, and then set the
> snapshot as the release following the release version specified by the user:
> <code>
> Resolve Project Dependency Snapshots.: 'com.sinapsi.libs:sinapsi-commons' set
> to release? (yes/no) yes: : yes
> What is the release version? 2.1.2: : 2.3.0
> </code>
> in this case the versions are:
> current: 2.1.2-SNAPSHOT
> release: 2.3.0
> next: 2.3.1-SNAPSHOT
> The plugin suggests to set the release version to 2.1.2, but the user can
> choice another version, eventually an already released version.
--
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
