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 tried this on an *.hs and a *.jhm file (JavaHelp formats) in a JAR that I had mounted. Sorry if this is a duplicate (I thought it was already filed, but I couldn't find it).
Created attachment 6578 [details] log file with the exceptions at the bottom
Set target milestone to TBD
The issue is now fixed by recent introducing of the attributes storage in the <jar-file>.nbattrs for each jar file mounted. However it's true that there can still be cases when the file's attributes will be readonly. For example if there is no .nbattrs file in a readonly folder (with writable files) then the attempt for .nbattrs creation fails. The problem is that AFAIK there is no API for finding out whether particular fileobject can be assigned attributes successfuly or not i.e. something like FileObject.canChangeAttributes(). Question for OPENIDE: Would it make sense to implement such API? As its purely filesystem's choice to implement the attributes storage the external clients are unable to find whether the storing of the attributes is possible or not.
verified in 3.5 (works on an .hs file that is in a jar).