This is really about providing access restrictions to the compiler. JDT has done this forever as OSGi requires it and it's possible with modern Javac compiler as well. It's more about what you tell the compiler to consider than our notions of scope.
On Apr 6, 2014, at 9:41 PM, Mark Derricutt <[email protected]> wrote: > On 7 Apr 2014, at 12:32, Benson Margulies wrote: > >> We then have other logical classpaths. . Something like javadoc should >> be able to define another named classpath structure; combining the >> dependencies of the plugin's implementation with dynamic code >> (doclets, whatever) seems like a category confusion to me. > > If we change/break this - can we PLEASE make the compilation path IGNORE > transitive dependencies of 'compile' dependencies - if I -need- it to > compile, -I- should depend on it up front. > > Mark > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > Thanks, Jason ---------------------------------------------------------- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl http://twitter.com/takari_io --------------------------------------------------------- To do two things at once is to do neither. -- Publilius Syrus, Roman slave, first century B.C.
