Thanks for the information, Geertjan. I appreciate you taking the time to go into detail about the flaws of my model.
Morn ________________________________ From: Geertjan Wielenga <[email protected]> Sent: Tuesday, October 9, 2018 12:18:53 PM To: dev Subject: Re: Exception when calling org.netbeans.Main#main You could try to embed the NetBeans editor into your framework: http://www.antonioshome.net/kitchen/netbeans/nbms-standalone.php Or you could integrate your docking framework into NetBeans, maybe these tips help: https://blogs.oracle.com/geertjan/plug-a-jidetabbedpane-into-the-netbeans-platform However, I'd advise strongly against all this. Either accept the NetBeans editor within the framework within which it is found or reject the framework, go with your own, and try and integrate some other editor. Here be dragons, in your approach, you'll spend a lot of time hacking things and with workarounds and so on. Yes, NetBeans is modular, but it makes more sense to embrace the framework in which the NetBeans editor is found than to try and hack it into your own for little benefit. Gj On Tue, Oct 9, 2018 at 8:11 PM morn hyland <[email protected]> wrote: > Hi Geertjan, > > > The reason I'm following this model is that I'm after the C/C++ editor and > debugger support that NetBeans provides via CND. I have an existing docking > manager and rich ecosystem that I'd like to incorporate NetBeans into. The > idea is to launch NetBeans from within the app and then re-parent views and > windows as need be. Do you have any specifics on why this model isn't > advisable? Is it possible to leverage the C/C++ editor and debugger > business logic without using the NetBeans window manager or UI? > > > Morn > > ________________________________ > From: Geertjan Wielenga <[email protected]> > Sent: Tuesday, October 9, 2018 9:12:40 AM > To: dev > Subject: Re: Exception when calling org.netbeans.Main#main > > Doesn't sound advisable. > > And FYI, this is Main: > > > https://github.com/apache/incubator-netbeans/blob/master/platform/core.startup/src/org/netbeans/core/startup/Main.java > > Gj > > > On Tue, Oct 9, 2018 at 4:59 PM morn hyland <[email protected]> wrote: > > > Hi NetBeans Gurus, > > > > I'm seeing a crash on starting up my NetBeans app with the following > > exception stack. The module bolded below differs on each run. Does this > > stack look familiar to anyone? > > > > java.lang.IllegalArgumentException: fixed or invalid: > > FixedModule:org.netbeans.modules.target.iterator > > at > > > org.netbeans.core.startup.ModuleList.computeProperties(ModuleList.java:950) > > at > org.netbeans.core.startup.ModuleList.moduleChanged(ModuleList.java:914) > > at org.netbeans.core.startup.ModuleList.flushInitial(ModuleList.java:834) > > at org.netbeans.core.startup.ModuleList.trigger(ModuleList.java:256) > > at org.netbeans.core.startup.ModuleSystem.restore(ModuleSystem.java:276) > > at org.netbeans.core.startup.Main.getModuleSystem(Main.java:156) > > at org.netbeans.core.startup.Main.getModuleSystem(Main.java:125) > > at org.netbeans.core.startup.Main.start(Main.java:282) > > at org.netbeans.core.startup.TopThreadGroup.run(TopThreadGroup.java:98) > > at java.lang.Thread.run(Thread.java:745) > > > > > > I'm trying something a little different to most other apps. I've wrapped > > NetBeans in a standalone Java app by calling org.netbeans.Main#main > > directly. Is there any other app out there following this model? > > > > > > Thanks in advance, > > > > Morn > > >
