[
http://jira.codehaus.org/browse/MRELEASE-399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161018#action_161018
]
Thomas Sauzedde edited comment on MRELEASE-399 at 1/15/09 9:17 AM:
-------------------------------------------------------------------
+1 for this proposal.
I'll also be happy to see such a behavior and not only for <dependency> but
also for the <parent> block !
In a sub-module, this will allow to use something like :
<parent>
<groupId>com.acme</groupId>
<artifactId>parent</artifactId>
<version>RELEASE</version>
</parent>
to stick to the newest <dependencyManagement> block defined in the "parent" and
when cutting a sub-module release, to have the proper, unique "parent" version
used by the release plugin at that time !
was (Author: tsauzedde):
+1 for this proposal.
I'll also be happy to see such a behavior and not only for <dependency> but
also for the <parent> block !
In a sub-module, this will allow to user something like :
<parent>
<groupId>com.acme</groupId>
<artifactId>parent</artifactId>
<version>RELEASE</version>
</parent>
to stick to the newest <dependencyManagement> block and when cutting a module
release, to have the proper, unique "parent" version used by the release plugin
!
> Replace dependency version for <version>RELEASE</version> 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:
> ...
> <dependency>
> <artifactId>b</artifactId>
> <groupId>ar.com.b</groupId>
> <version>RELEASE</version>
> </dependency>
> ...
> 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 <version>RELEASE</version> with <version>1.2.0</version> ?
> 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
> <version>RELEASE</version> 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
