> In detail, I suggest to have Maven core adopt the approach taken by the
> Enforcer Plugin [0] regarding normalization of the version with the
> deviation to consider only the first three numeric parts (assume missing
> parts to be 0) for the comparison. This should make profile activation more
>
Although Sun's JDK versioning is a non-standard format, I think it's
obvious Sun isn't going to change it soon. (I've been watching the
JSR-294 debate! Yup, they are not changing.) I am +1 on Maven
supporting parsing this special format to make the patch releases
(_XX) naturally comparable with the
On 2010-01-02, at 10:00 AM, Benjamin Bentmann wrote:
> Benjamin Bentmann wrote:
>
>>
>>test
>>
>> (1.4,1.5]
>>
>>
>> Now, when do you think does this profile get activated in case the current
>> Java version (as given by ${java.version}) happens to be
>> a) 1.4.0_07
>> b)
It is many more logical. But we'll have to clearly document it because
many users will wrongly suppose they avoid all 1.4 versions with (1.4
Arnaud
On Saturday, January 2, 2010, Benjamin Bentmann
wrote:
> Benjamin Bentmann wrote:
>
>
>
> test
>
> (1.4,1.5]
>
>
>
> Now
Benjamin Bentmann wrote:
test
(1.4,1.5]
Now, when do you think does this profile get activated in case the
current Java version (as given by ${java.version}) happens to be
a) 1.4.0_07
b) 1.4.0_14
c) 1.4.2_07
d) 1.5.0_07
e) 1.5.0_14
f) 1.5.1_14
For better illustr
Hi,
as per MNG-1957, Maven introduced support to activate profiles based on
a version range for the JDK version:
test
(1.4,1.5]
Now, when do you think does this profile get activated in case the
current Java version (as given by ${java.version}) happens to be
a)
