On Thursday 30 March 2006 08:55, Enrique Rodriguez wrote: > The jars you point out at iBiblio are not > consistent with M2 naming.
Besides your expression of the NIH syndrome (others don't know what they are doing, so I will show them), could you explain why those are not consistent with M2 naming? The Specification != the Jars required. If there are changes needed to those jars irrespectively of changes to the specification, are you then start calling them 4.0.1 and so forth? What if you actually hit an Java incompatible change, that was missed out? Is that then a 4.0.2, although it will break builds? The approach of "whomever" makes a lot more sense to me, and is definately not "a matter of fact" as you are trying to put it. Cheers Niclas
