Martin Höller wrote at Dienstag, 24. März 2009 14:48:
> 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
Actually this thread simply displays Todd's and my disagreement (or at least
different experiences) ;-)
For the records: We originally used properties and it stopped working with
2.0-beta-5, not with 2.0-beta-6. However, at that time we used the
properties directly in the deps of the children and not in the depMgmt of
the parent. Additionally if you look at the resolved issues, there has been
a lot of work done regarding this.
Funny thing is that we use now for quite some time exactly the described
scenario of Martin, but with explicit versions in the depMgmt and it works
for us.
- Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
