[
https://issues.apache.org/jira/browse/MRELEASE-220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16558141#comment-16558141
]
Frédéric Combes edited comment on MRELEASE-220 at 7/26/18 10:32 AM:
--------------------------------------------------------------------
Hi,
I currently experiment the same problem with version 2.5.3, with
`updateDependencies=false`, at the end the internal dependencies in the pom are
updated to SNAPSHOT instead of staying at RELEASE version.
This bug was closed for cleanup, is there a way to reopen it for fixing the
problem ?
Regards
Fred
was (Author: fcombes):
Hi,
I currently experiment the same problem, with `updateDependencies=false`, at
the end the internal dependencies in the pom are updated to SNAPSHOT instead of
staying at RELEASE version.
This bug was closed for cleanup, is there a way to reopen it for fixing the
problem ?
Regards
Fred
> Add property to keep released versions for dependencies
> -------------------------------------------------------
>
> Key: MRELEASE-220
> URL: https://issues.apache.org/jira/browse/MRELEASE-220
> Project: Maven Release Plugin
> Issue Type: Improvement
> Components: prepare
> Affects Versions: 2.0-beta-4
> Reporter: Daniel Beland
> Assignee: Emmanuel Venisse
> Priority: Major
>
> 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
(v7.6.3#76005)
