On Sat, Jul 14, 2018 at 1:00 PM, Eirik Bakke <[email protected]> wrote:
> One of the great things about the NetBeans module system is that adding a > dependency on module X does _not_ permit you to use classes from X's own > dependencies (transitive dependencies). > In Jigsaw, module X can for each of its dependencies decide if it should be transitive or not. If it says "requires foo", that users of "X" won't be able to use stuff from "foo" without explicit dependency on "foo", if it says "requires transitive foo;" then users of "X" will be able to use stuff "foo" without explicitly depending on "foo". Jan > > Is this also the case with Jigsaw? > > -- Eirik > > On 7/14/18, 1:35 AM, "Laszlo Kishalmi" <[email protected]<mailto: > [email protected]>> wrote: > > Well this question is to Jaroslav Tulach mostly. > > From Java 9 there are three modularization system in Java. OSGI, > NetBeans and Java's JigSaw. > > My question is could NetBeans be ported on JigSaw? What would we gain > form that movement (if any), and what would be the pain points. > > I'd even would like to see a deep analysis on this topic on Jarda's blog. > > > Thank you in advance! > > Laszlo Kishalmi > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > <mailto:[email protected]> > For additional commands, e-mail: [email protected] > <mailto:[email protected]> > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > > >
