This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | Restart NetBEans IDE don't submitted changes in conf file | ||
---|---|---|---|
Product: | platform | Reporter: | peter_rogge <peter_rogge> |
Component: | Launchers&CLI | Assignee: | Jaroslav Tulach <jtulach> |
Status: | RESOLVED WONTFIX | ||
Severity: | blocker | ||
Priority: | P4 | ||
Version: | 6.x | ||
Hardware: | PC | ||
OS: | Linux | ||
URL: | http://www.netbeans-forum.de/viewtopic.php?f=4&t=3009 | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
peter_rogge
2009-07-11 10:39:34 UTC
I also try the old restart-method from Joschs NetBeans Blog http://www.sepix.de/blogs/blogrittner/blog/archive////beandev_neustart_der_netbeans_platform/index.html (German) with the some results -> under Windows restart correct, under Linux/Unix not. See also the discussion in http://www.netbeans-forum.de/viewtopic.php?f=4&t=3009&p=12998#p12998 (German). The restart seems to be handled by o.n.bootstrap/launcher/unix/nbexec however the configuration file is read by apisupport.harness/release/launchers/app.sh which in turn calls the nbexec. When you request the restart, the call does not propagage to app.sh and that is why the config file is not re-read. The situation in Windows is likely different, as the nbexec is a DLL linked with the whole app.exe, so the control returns back to the code that actually reads the config file. I was thinking about two ways to fix the problem: 1. pass the location of conf file to nbexec in some system property, make sure it is re-read on restart 2. tell nbexec to return the control to the app.sh via some property, so app.sh can re-read the config file. I don't really like any of these solutions and I don't want to bother implementing any of them. If you however can provide a patch, I am ready to evaluate it. Meanwhile marking as "won't fix". |