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.
Without any work anywhere else the developer can just go ahead and put this new attribute in <module>/manifest.mf but it would be better if we do it this way: * extend the module build infrastructure (ie harness) so that it looks for a property "show.in.autoupdate.client=true/false" in nbproject/project.properties and generates the corresponding AutoUpdate-Show-In-Client: true or false in MANIFEST.MF * If show.in.autoupdate.client is missing then generates true (show) for regular modules and false (hide) for autoload and eager modules * Of course if the developer already specifies AutoUpdate-Show-In-Client in <module>/manifest.mf then it takes precedence validate-catalog ant task should be adapted accordingly to recognize this new manifest attribute
There is no purpose for putting such an attribute in project.properties; it should be written directly in manifest.mf. I can still set a default value, in <jarwithmoduleattributes>.
Checking in JarWithModuleAttributes.java; /shared/data/ccvs/repository/nbbuild/antsrc/org/netbeans/nbbuild/JarWithModuleAttributes.java,v <-- JarWithModuleAttributes.java new revision: 1.14.26.1; previous revision: 1.14 done