On 18/09/2009, at 6:00 PM, Stephen Connolly wrote:
To avoid the last issue, I would use versions like this:
1.4.2_05
1.4.2_19
They will continue sorting correctly for version ranges as long as
we never
get into 1.4.12 which given the history of Java versioning is pretty
unlikely.
Then yo
2009/9/18 Brett Porter :
>
> On 18/09/2009, at 6:41 AM, Stephen Connolly wrote:
>
>> Of course we then hit the question, how should we divide things up? in
>> the
>> following bgid=org.codehaus.mojo.animal-sniffer
>
> This is an unusual case. Each of these signatures is a different artifact,
> not
On 18/09/2009, at 6:41 AM, Stephen Connolly wrote:
Of course we then hit the question, how should we divide things up?
in the
following bgid=org.codehaus.mojo.animal-sniffer
This is an unusual case. Each of these signatures is a different
artifact, not a version of the same artifact IMO,
these are signatures of the entire javase classpath
not the actual classes
Sent from my [rhymes with tryPod] ;-)
On 17 Sep 2009, at 22:19, Jörg Schaible wrote:
Stephen Connolly wrote:
OK, here is the problem set:
For animal-sniffer, we need to have signatures of each of the java
runtime
Stephen Connolly wrote:
> OK, here is the problem set:
>
> For animal-sniffer, we need to have signatures of each of the java runtime
> libraries (i.e. the animal smells/scents)
So, you mean, you will have a POM for the rt.jar ?
> That way animal-sniffer can detect whether you are compatible w
