Benson Margulies wrote: > There is perhaps a communications problem here. I don't think this is > about ranges. I suspect that it is about: > > - project g:A version 1 depends on x:y:2.0 > - project g:B version 1 depends on g:A:1 and x:y:1.0 > > What ends up in the classpath of B? x:y:2.0, I think.
So what? Should or can Maven now somehow detect that g:B uses stuff of x:y:1.0 that is no longer available in x:y:2.0? If it does not, it is not helpful at all, if some mechanism ensures that g:B runs with x:y:1.0 only. - Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
