Ordering of versions

[Brian Pontarelli]

It seems to me that the version scheme for a single module only impacts that module and not its dependencies. When the dependency graph is completely built and then traversed, modules are compared based on their scheme with all the other instances of themselves in the graph. Therefore, I don't think it impacts others at all.

Thoughts?

-bp


On Nov 14, 2011, at 7:49 AM, Peter Kriens wrote:

> Gili,
> Can you explain how this would work when my modules use a different scheme than yours?
> 
> Kind regards,
> 
> 	Peter Kriens
> 
> On 13 nov. 2011, at 04:59, cowwoc wrote:
> 
>> 
>> mark.reinhold wrote:
>>> 
>>> Support such semantics, sure, but I'm not sure it should prescribe them.
>>> OSGi and Maven have established some useful and widely-used conventions
>>> around version semantics but I've seen developers and customers use all
>>> sorts of other wild and woolly version schemes over the years.  I'm not
>>> convinced that a standard Java module system should require people to
>>> abandon such schemes, unless they're just really totally broken.
>>> 
>> 
>> Mark,
>> 
>> If at all possible, please consider allowing users to specify a
>> Comparator<Version> (or Comparator<String> depending on your taste) on a
>> per-module basis. This would allow users to use any versioning scheme they
>> see fit.
>> 
>> Gili
>> 
>> --
>> View this message in context: http://jigsaw-dev.1059479.n5.nabble.com/Ordering-of-versions-tp4970773p4988030.html
>> Sent from the jigsaw-dev mailing list archive at Nabble.com.
>