[
http://jira.codehaus.org/browse/MRELEASE-220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=165292#action_165292
]
Peter Liljenberg commented on MRELEASE-220:
-------------------------------------------
After digging into the code it looks like the actual bug is in ReleaseManager
rather than the plugin itself:
//MRELEASE-220
if ( mappedVersion != null && mappedVersion.endsWith(
"SNAPSHOT" ) &&
!dependencyVersion.endsWith( "SNAPSHOT" ) &&
!releaseDescriptor.isUpdateDependencies() )
{
return;
}
Shouldn't we check the dependencyVersion here?
if ( !dependencyVersion.endsWith( "SNAPSHOT" ) &&
!releaseDescriptor.isUpdateDependencies() )
{
return;
}
> Add property to keep released versions for dependencies
> -------------------------------------------------------
>
> Key: MRELEASE-220
> URL: http://jira.codehaus.org/browse/MRELEASE-220
> Project: Maven 2.x 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 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
