[
http://jira.codehaus.org/browse/MRELEASE-583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=235373#action_235373
]
Elliot Metsger commented on MRELEASE-583:
-----------------------------------------
bq. I also wonder if it might be better to allow not setting a development
version.
I agree, it would be nice to not require a development version. I've run
across both of those usecases when using the release plugin.
I also agree that the y/n prompt is annoying/superfluous.
{quote}How about:
Dependency g:a:v is a snapshot (2.1.2-SNAPSHOT)
Version to use for the release (2.1.2): ?
Version to use in development (2.1.3-SNAPSHOT): ? (-- based on selected release
version){quote}
So just to confirm, the prompt for the development version would allow:
{{2.1.3-SNAPSHOT}} (the default)
{{2.1.2}} (accommodating the first usecase)
{{2.1.2-SNAPSHOT}} (accommodating the second usecase)
I like it!
> 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
> 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
