On 11/17/2010 12:17 AM, Uwe Schäfer wrote:
Hi fellow Wicketeers
i am quite puzzle due the maven behaviour described below. I took this
to the maven mailinglist, but with no result.
I think it is crucial to other projects (such as wicket) to have a pom
working no matter what version of maven the user has, especially for
archetypes.
maybe we find a maven "maven" in here, who could shed some light on the
issue below?
cu uwe
All is fine as long as I specify a certain version, e.g. 1.4.13
But using a version range does not work, e.g. [1.4.10,1.5)
well, that´s just spooky!
i tried to reproduce this and while maven 2.1 interprets [1.4.10,1.5) as
we would expect and chooses 1.5-SNAP, maven 2.2.1 as well as 3.0
cannot cope with such a range.
modifing the range to have the same "depth" like
[1.4,1.5) now works again in 2.2.1 and 3.0, but for some weird reason
(smell like char comparision instead of numbers?) it now chooses 1.4.9.
if that 1.5 snapshot should be in or out probably is a matter of
discussion with the maven folks:
[MNG-4751] - Snapshot version not resolved for version range
this probably is something for the maven list, even though the outcome
would be interesting for any maven project.
Have you tied the wicket quickstart for maven?
http://wicket.apache.org/start/quickstart.html
that´s what i went with playing with the wicket-version property.
cu uwe
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
