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: | User-installed modules use incorrect layer for settings | ||
---|---|---|---|
Product: | platform | Reporter: | Svata Dedic <sdedic> |
Component: | -- Other -- | Assignee: | Jesse Glick <jglick> |
Status: | CLOSED FIXED | ||
Severity: | blocker | CC: | jpokorsky, ttran |
Priority: | P1 | ||
Version: | 3.x | ||
Hardware: | Other | ||
OS: | Linux | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
Svata Dedic
2001-10-04 10:07:19 UTC
*** Issue 16218 has been marked as a duplicate of this issue. *** Jan what controls this? I know that NbInstaller.loadLayers will in this case insert the module layer into ModuleLayeredFileSystem.userModuleLayer rather than .installationModuleLayer, or at least this is what it is supposed to do. Anyway SystemFileSystem.createWritableOn should not care, it should return PRJ_FS in this case...right? If there is some problem in org.netbeans.core.modules.* I can try to fix it, but I do not know exactly what SFS is supposed to be doing in this case. Please note that #16218 was a P1. I think this issue needs to be resolved for the Beta. Upgrading to P1. SFS.createWritebleOn decides between project layer and user layer in accordance with SFS.project attribute. Default is the user layer(session). If file does not contanin attribute its parent is checked. Once the file is located on any writable filesystem SFS.createWritebleOn always returns this one. assigned back to Jesse. Found the problem with Jan P.'s help. In the case of a user-installed module, the SFS was in fact returning the writable filesystem the file was defined on. However this was not quite what was wanted: it should only do this in case the file is in fact in a writable subdelegate of that filesystem, if the defining filesystem was a ModuleLayeredFileSystem. Not really a modules bug as such, rather projects system. Fixed in SystemFileSystem.java 1.19. verified Resolved for 3.4.x or earlier, no new info since then -> closing. |