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.
I'm confused over exactly what the various capabilities properties of a filesystem do, and the documentation doesn't really help. I have a directory containing some library classes used by the ones I'm working on, so I mounted it as a Local Directory filesystem. Since they're library files, I set the fs property for Read Only, but I wasn't sure about the Capabilities settings, in particular the Use in Compiler one. The tooltip in the propert editor says "(r/w) If True, these files are part of the classpath for compilation", which suggests I need it set to true to avoid errors when the import statements can't find them. However, the "Disabling Compilation for a Filesystem" help file entry says "You can disable compilation on a mounted filesystem. This feature is particularly useful if you mount a library to browse its sources but you do not want it to be recompiled every time you compile an application that is dependent on the library." which suggests I need it set to false to avoid it recompiling the library classes. Yet the "Configuring a Mounted Filesystem" help file entry says "If you select the Capabilities tab of the property sheet, you can set or disable the availability of that filesystem for compilation, ..." so if I do set it false, then it won't be available for compilation - does that include compilation of the other fs' classes or just its own? So, the different descriptions appear to be giving conflicting advice and I'm left just as confused as to the "correct" setting... No big deal, since it builds and runs okay, but the docs could certainly be a lot clearer.
Target milestone was changed from '3.4' to TBD.
reassigne to David for evaluation, thanks in advance
reassigne to David
assigning (although I'm not sure I'm right - correct me if needed).
OK. I understand the confusion. For what it's worth, the descriptions are *not* contradictory, though this may not be so obvious. The key is the statement "This feature is particularly useful if you mount a library to browse its *sources*". If you mount a JAR file that does not contain sources (i.e. .java files) but only .class files (which I think is the case most of the time when you mount a library), then there is no reason to change this value to False (a class file can't be recompiled without accompanying .java files). The main use case here is that someone, when debugging, wants to be able to view the source code of the library that their app calls. I'll try to make this more explicit.
fixed in trunk /cvs/usersguide/javahelp/org/netbeans/modules/usersguide/filesystems/filesystems_disable-compile.html new revision: 1.14; previous revision: 1.13