So let's think how this would work in a project dependency tree world... For each node in the tree we would need to provide:
1. Any coordinates of artifacts that are provided by this artifact (or a compatible implementation is provided)... in most cases this will be empty, but still 2. Any coordinates of artifacts that are depended on by this artifact. 3. The version of this artifact that was resolved at build time 4. The version range of this artifact that is "acceptable" 5. (Optional, but highly recommend) the SPDX license code for this artifact And then we add 6. The version number comparison strategies (yes that's a plural) plus the epoch information to decode when the rules should be applied. Now #6 needs to be platform neutral... so probably some JavaScript function within a defined helper API... I do not think we should go down that road... so either we just say: "here is the version comparison rules and spec, if you want to play in central, play in central by these rules" OR We say version comparison is build time concern and the the builder pom declare its version comparison rules OR ? Insert alternative suggestion here ? On Sunday 25 September 2016, Hervé BOUTEMY <[email protected]> wrote: > Le dimanche 25 septembre 2016 13:21:27 Karl Heinz Marbaise a écrit : > > If you start thinking about version comparison in detail (I have > > started with this a little bit ;-( ) it will become really a > > nightmare...and really hard... > > > > What happens with artifacts in your repository manager if you change the > > version comparison ? Can you reuse them ? What happens if two people use > > different comparisons can they use the same repository to share their > > artifacts which includes their transitive dependencies (which implies > > the comparison) ? This are only a few question which I have started > > with? Which brings a extreme complexity which I have to admit can't > > handle... > +1 > I see you started to really think at it in details and found the key issue: > that's where the little extensions idea becomes a mess in real world... > > Regards, > > Hervé > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] <javascript:;> > For additional commands, e-mail: [email protected] <javascript:;> > > -- Sent from my phone
