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.
Libraries from WEB-INF/lib are always mounted as a new filesystem regardless of preexisting mounts, i.e. if I use the same taglib in two WEB-INF then the jar is mounted twice
How can we discover that they are identical? It might be more natural when we introduce project concepts
this will be fixed when we stop mounting libraries from WEB-INF in 4.0
As a user I'd like to put in a request to fix in 3.5. Filesystems are a performance hit on NB since they are parsed and processed, taking CPU time and memory (at least that's my limited understanding). By mounting the same filesystem repreatedly, isn't that going to increase the performance hit? Is it very hard to add a check based on the archive file property before adding to the filesystem list?
Currently mounting of libraries is the only natural way how to make them available for compilation / code completion and many other types of functionality. This is in my understanding what Ales complains at according to summary. We are going to address this with new projects where filesystems are not equal to classpath. OTOH his initial comment implies that some mount points are duplicated. This is dup of issues like 29675. It should be already fixed for 3.5 and you are right there can be performance hit. Of course performance is not the only reaon why to fix bugs ;-)
fixed in projects branch
Since I just fixed another issue with mounting I was trying to reproduce this and look at the bug. I do not see how exactly reproduce this. I've created a tld in netbeans, added a tag, had a handler generated and created a jar for it. The I've created 2 web modules. I added the taglib into both web modules. I tried both ways of adding them: directly from filesystem and by first adding them into taglib repository and then into a web module. Both ways end up creating a _copy_ of the jar file in each web module. Of course that when you update the tag lib the jar files are not automatically updated in the WEB-INF/lib folders of web modules. This means they are 2 different jar files and need to be mounted separately. If this was an issue it is not a defect, 'fixing' it would create a defect. If I make not sense here, please reopen. It would be desirable feature to keep the jar file at one place and copy it automatically into any web module that wants to use it (and then perhaps mount it once) but that is a separate issue. File it as enhancement if you like.