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.
If you mount filesystem with jar file in it, the jar file is not correctly recognized and pop up menu for it will offer to convert it to text!!! Then you can open that "text" file and edit!!! it in editor and then save!!! Jar file was created from command line and by ant script. Also was tested if jar file was copied into already mounted file system.
In my opinion that is a feature. But anyway why do you think this is a problem in core?
I don't think that it's a feature to allow user to modify and save binary file (opened as text file), it could destroy users data at glance. I thought that it is somehow connected with with filesystems, but I could be wrong. Note: If you mount filesystem with "known" files, they are correctly recognized and treated so. So why should we have different policy for java archives and let users to modify them as text files.
That's feature. Convert to text action appear on all default data objects, e.g. all objects which no module dataLoader took over them. These default dataobjects don't offer any functionality, therefore text module, if present, adds the Convert to text action to them, to have some possiblity for user to work with such files via IDE. Of course there is not recognition if the files are binary or not. Its up to user to use it correctly, just like working with files on disk. In this case, it doesn't mean that jar file wasn't recognized. JarPackager tooks only over .jar files with .jarcontent (default set) sibling file. So in this case probably only .jar without .jarcontent was present so no DataLoader took it but DefaultDataLoader. Therefore I marked the issue as WONTFIX.
Resolved for 3.3.x or earlier, no new info since then -> closing.