Baptiste, Thanks for answering.
Yes, the dependency I ´m talking about would be a dependency between two projects of my own (please note I ´m not using multi-module approach so the project I 've developed my own and I depend is almost used as a library). I knew about the special keyword RELEASE, I was trying it with my own projects. I 'm using it because i 've a two level hierarchy of parent poms, in the root level i define all dependencies versions using dependency management, in the next (intermediate) level i may have different parent poms according to the different nature of my projects but that parent pom will only define generic dependencies for projects of that nature it won't define version for that dependency as all versions will be defined on the root pom. So a project's specific pom would inherit from the intermediate level pom. The fact is that whenever I need to add a dependency to a specific project pom I would have to modify the root pom to add the dependency version in dependencyManagement and the specific (leaf) pom to add the dependency itself. The problem for me is that not only I need to make a release of the two projects i 've modified (root and leaf), but also i need to release the intermediate level om so that it now references the new version of the root pom. I thought of that as too much version handling so i tried to reference parents version as RELEASE. (I 've also tried RELEASE keyword on some other depenencies, not parents, of my own). The final problem is that when i make a release (with the release maven plugin) the released pom also talk about the parent or dependency with version "RELEASE", that's not good for me as I think that a release version must be repeatable but this way your specific leaf project release behaviour could change if you make a new release of some parent or a dependency. That's why i 'm proposing to maven-release-plugin developers to modify the RELEASE keyword of a dependency by it's resolved dependency version on compile or release time. After all that.., i asked myself about the help:effective-pom goal..., and i realised that the maven-release-plugin acted the same as help:effective-pom keeping versions as RELEASE... In my opinion keeping the RELEASE keyword after calculating the effective pom is by instance, hiding to me which will be the real version used to compile that project. So, why not change the help:effective-pom (and maven-release-plugin) goal to replace special keyword RELEASE to by the real version used?? thanks, and sorry for the text lenght i 'm just trying to get myself explained :D cheers! On Fri, Dec 19, 2008 at 5:57 PM, Baptiste MATHUS <[email protected]> wrote: > Which plugin or dependency is it? Is it one of yours of another? > RELEASE is a special keyword that is designed to be resolved at runtime > against the latest *non-snapshot* version. > > Cheers > > 2008/12/19 Nicolas Barrera <[email protected]> > > > Hi, (sorry if i double posted, i 'm resending because i had a send error > > last time) > > > > Here is my question: > > > > Why is it that whenever I execute help:effective-pom and I got some > > dependency or parentPom defined with <version>RELEASE</version> > > > > in the effective-pom output i still see <version>RELEASE</version> and > NOT > > the truly version number I 'm compiling against. > > > > hope sombody answers this one :) > > > > cheers! > > > > > > -- > Baptiste <Batmat> MATHUS - http://batmat.net > Sauvez un arbre, > Mangez un castor ! >
