This seems sensible and not unfamiliar with how import statements already work in Java to determine the fqn to search for a given class.
On Fri, Feb 17, 2017 at 4:07 AM, Michael Rasmussen < michael.rasmus...@zeroturnaround.com> wrote: > On 17 February 2017 at 01:19, Stephen Colebourne <scolebou...@joda.org> > wrote: > > > > However, I remain of the opinion that they are highly dangerous for > > the wider ecosystem without some additional ability to qualify them. > > The are many more private jars than public jars, and the clashes seen > > today on Maven Central are just the tip of the iceberg of this > > problem. > > > I can only agree with this. s/willow/spark/ and we have an example of such > a situation in maven already today, of two different libraries with the > same name. > With the options to specify group, no problem, then I could just write: > requires spark-core from com.sparkjava or requires spark-core from > org.apache.spark in order to clarify which was intended. > > /Michael >
