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.
When I select global installation in the update center dialog, the module seems to be installed correctly (under <nbdir>/modules/), but it cannot be enabled because some libs are always expected to be in the user's module dir (the libs are actually in D:\DevTools\Netbeans-3.6\modules\profiler-ea-libs): java.lang.Exception: Problem with a required JFluid installation subdirectory D:\DevTools\Netbeans-3.6\users\lars\modules\profiler-ea-libs Original message: File does not exist at com.sun.tools.profiler.GlobalSettings.setJFluidDirs(Unknown Source) at org.netbeans.netfluid.Profiler.<init>(Unknown Source) at org.netbeans.netfluid.Profiler.getDefault(Unknown Source) at org.netbeans.netfluid.NetfluidModule.restored(Unknown Source) at org.openide.modules.ModuleInstall.installed(ModuleInstall.java:75) at org.netbeans.core.modules.NbInstaller.loadCode(NbInstaller.java:359) at org.netbeans.core.modules.NbInstaller.load(NbInstaller.java:263) at org.netbeans.core.modules.ModuleManager.enable(ModuleManager.java:861) at org.netbeans.core.modules.ModuleList.installNew(ModuleList.java:552) at org.netbeans.core.modules.ModuleList$Listener.stepEnable(ModuleList.java:2116) at org.netbeans.core.modules.ModuleList$Listener.access$2100(ModuleList.java:1743) at org.netbeans.core.modules.ModuleList$5.run(ModuleList.java:1974) at org.openide.filesystems.EventControl.runAtomicAction(EventControl.java:89) at org.openide.filesystems.FileSystem.runAtomicAction(FileSystem.java:417) at org.netbeans.core.modules.ModuleList$Listener.run(ModuleList.java:1950) at org.openide.util.Task.run(Task.java:136) at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:330) [catch] at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:686)
*** Issue 47170 has been marked as a duplicate of this issue. ***
*** Issue 47236 has been marked as a duplicate of this issue. ***
*** Issue 47231 has been marked as a duplicate of this issue. ***
This is a known limitation of the first release (M1), will address in M2.
Fixed for M2, profiler can now work both globally and inside the userdir. FYI: M2 is planned to be released during the last week of September.
Verification of old issues.
Closing old issues.
Reverting to the original Target Milestone value changed by mistake. Sorry for inconvenience.