[
http://jira.codehaus.org/browse/MRELEASE-399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161498#action_161498
]
Nicolas Adrian Barrera commented on MRELEASE-399:
-
Thomas,
I 've been working on the plugin source code for a while before going on
holidays for the last 2 weeks and I could made some changes on the source to
replace the parent version from RELEASE to the last release resolved version.
I wasn't sure if those changes were alright so I didn't post them as I 've
never collaborate on an open source project yet I don't know how should I share
my changes...
Perhaps I post them later as a diff between the base working copy with only
those changes included and the svn tag I 've download.
comments are welcome.
cheers
> Replace dependency version for RELEASE dependency.
> -
>
> Key: MRELEASE-399
> URL: http://jira.codehaus.org/browse/MRELEASE-399
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Components: prepare
>Affects Versions: 2.0-beta-8
>Reporter: Nicolas Adrian Barrera
>
> I 'm using RELEASE version for some dependencies in my current project.
> Imagine a simple scenario where i have project A who depends on project B...,
> A's pom.xml states:
> ...
>
> b
> ar.com.b
> RELEASE
>
> ...
> When running "mvn compile" to A, there maven knows which is B's last released
> version so that it can compile against certain specific code at that time,
> imagine it is 1.2.0.
> So why when I run "mvn release:prepare" A's tagged (released, svn cp) pom.xml
> doesn't replace RELEASE with 1.2.0 ?
> Why do i think it should?
> * So that A's released version will always work the same as that day I
> performed A's release
> * So that A's released version won't get hurted by possible
> non-backward-compatible changes on future B's releases
> I 've read at the Maven Definitive Guide e-book that use of
> RELEASE is not encouraged, but i seemed helpful for me
> until this point where I find this quite dissapointing.
> Please feel free to share thoughts may be I got confused with this but i
> think this is a problem that worth to be solved.
--
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
