On 03.08.2012 12:23, Robert Elliot wrote: Hi Robert,
Would there be any appetite for adding other jars to version99.qos.ch?
Appetite? No. However, it's something we can support (please read on).
There are various jars in maven central that are composites of other jars. Maven's transitive dependency behaviour makes it very difficult to prevent those composite jars creeping on to the classpath, introducing multiple different versions of the same class. For example, if you want to use hamcrest 1.3 with junit 4.10 you can do so by bringing in junit:junit-dep:4.10 and org.hamcrest:hamcrest-core:1.3; however, it only requires one transitive dependency to bring in junit:junit:4.7 (which combines the classes from junit:junit-dep:4.7 and org.hamcrest:hamcrest-core:1.2) and it's going to be random whether you get the 4.10 or the 4.7 versions of the junit classes and the 1.2 or 1.3 versions of the hamcrest classes.
While I understand what you are trying to explain I don't see how it matches what is effectively found in junit jar files. For example, both junit:junit:4.7 and 4.10 contain classes from the org.hamcrest package. What am I missing?
A junit:junit:99-empty in version99.qos.ch would solve this issue.
Bit cheeky to piggy back on qos.ch, but it would be very useful...
Yes, it would be cheeky bordering on rude. I am for publishing junit:junit:99-empty but only if the Junit folks *officially* sanction it. In any case, I very much appreciate the proposal. Best regards, -- Ceki http://tinyurl.com/proLogback