I was part of that discussion but I don't consider myself a Maven expert yet.
However I did go away from the conversation and made a very simple maven
multi-module project and ran a release on it. I ensured the project had
dependencies between modules and the release worked without having to perform
an install first and when using ${project.version}.
Can anyone definitively answer if this is the correct way to do it? Or is using
the string directly the correct way? Or is either way consider correct ;-).
---
Todd Thiessen
> -----Original Message-----
> From: Martin Höller [mailto:[email protected]]
> Sent: Tuesday, March 24, 2009 9:49 AM
> To: Maven Users List
> Subject: Re: Release plugin and multimodule interdependent childs
>
> On Tuesday 24 March 2009 Reinhard Nägele wrote:
> > I don't have a solution to your problem, but I would advice against
> > putting the real version number instead of
> ${project.version}. It is
> > good practice to avoid such redundancy using
> ${project.version}, even
> > though the release plugin can deal with explicit versions. Using
> > ${project.version} is also suggested by "The Definitive Guide"
> >
> (http://www.sonatype.com/products/maven/documentation/book-defguide).
>
> And in this thread [1] it was recommended to use the real
> version instead of ${project.version}.
>
> So what is the real truth?
>
> - martin
>
> PS: We are using the version string, having the release
> plugin update it
> without any problems here.
>
> [1] http://www.nabble.com/forum/ViewPost.jtp?post=22340527&framed=y
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
