You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@codehaus.org> on 2014/11/25 22:39:28 UTC
[jira] (MRELEASE-220) Add property to keep released versions for
dependencies
[ https://jira.codehaus.org/browse/MRELEASE-220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Osipov closed MRELEASE-220.
-----------------------------------
Resolution: Won't Fix
Please refer to https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014 if you're wondering why this issue was closed out.
Assignee, if you think you can fix this bug anytime soon, please reopen and proceed appropriately.
> Add property to keep released versions for dependencies
> -------------------------------------------------------
>
> Key: MRELEASE-220
> URL: https://jira.codehaus.org/browse/MRELEASE-220
> Project: Maven Release Plugin
> Issue Type: Improvement
> Components: prepare
> Affects Versions: 2.0-beta-4
> Reporter: Daniel Beland
> Assignee: Emmanuel Venisse
>
> When I release a project with many modules with internal dependencies.
> I would like those dependencies to keep the released version rather than the next development version.
> ie: I only release some modules at a time (those that were changed only since last release).
> So when my webapp is released, I want it to become SNAPSHOT again(as it is done already) but want the internal dependencies to keep the released version.
> I want to update them manually whenever I change one.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)