Hi The Java module system does permit adding/removing (root) modules, and thus modifying the module graph at runtime. This is done through the layer API of the JPMS. A layer would needed to be created (by netbeans under the hood) for each module (and possible dependencies) at the time it is requested to be added to netbeans.
I for once think that moving longterm to the new java module system would be great to modernise netbeans Regards M Am Sa., 14. Juli 2018 um 08:40 Uhr schrieb Geertjan Wielenga <geertjan.wiele...@googlemail.com.invalid>: > Jigsaw does not permit updates at runtime. So if we were to use Jigsaw, > that would be the end of being able to install plugins into Apache NetBeans > while it is running. > > Gj > > On Saturday, July 14, 2018, Laszlo Kishalmi <laszlo.kisha...@gmail.com> > 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: dev-unsubscr...@netbeans.incubator.apache.org > > For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org > > > > For further information about the NetBeans mailing lists, visit: > > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > > > > > > >
