sdedic opened a new pull request, #4301: URL: https://github.com/apache/netbeans/pull/4301
The module system offers several options for module management. `--enable` option seems to work well, as it directly calls `ModuleManager.enable` and enables the requested modules (+ dependencies) on the fly. But `--disable` was implemented for some reason through delayed-disable, but **unlike** plugin UI, it will not generate the next-startup information files and does not request a restart: it seems broken. I filed [NETBEANS-6516](https://issues.apache.org/jira/browse/NETBEANS-6516) to track this, Option that would **disable modules on the fly** is missing completely. This was removed from the UI, perhaps because **removing** code from the memory is hard: there may be half-linked dangling listeners etc. But the option processing happens during startup before the UI even appears, so it seems a lot safe. I have implemented `--direct-disable` option that allows to disable one or more modules; the state will be persisted in the user directory config area. It will error out and abort the execution in case of any error, such as another not disabled module that depends on the one that should be disabled. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
