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.
' During the manual installation of my module through update center, I would like my module to be installed globally into the NB's installation directory by default. Basically, I want the "Global" check box to be checked automatically on the update center wizard's "View Certificates and Install Modules" page upon the installation of my module. ' - Isao Yanagimachi, HP This is important to the Minex team as alot of our updates have binaries from the bin directory, and the update doesn't work at all if it isn't global, and it is too much to ask every single user every time to check the global box and get it right.
> our updates have binaries from the bin directory Do you mean from your.nbm/netbeans/bin? In that case "Global" checkbox will be checked automatically and (even more) it won't be possible to uncheck it. Is it sufficient behaviour?
> In that case "Global" checkbox > will be checked automatically I've never seen this behaviour, it is a recent thing? But for us it is .nbm/minex5/bin because our product is called Minex5 not Netbeans, would this have any effect? Also I do not think that covers all use cases. Honestly we would like it to be 'Global' all the time, i cannot think of when we would have user installation of modules. Minex5 doesn't offer as many modules as netbeans, and each of our modules are quite large.
ok, so I suggest to add new attribute "global" to info.xml, defining behaviour of "Global" checkbox. Possible values: "default" -> "Global" will be checked by default "mandatory" -> "Global" will be checked by default and it won't be possible to uncheck it other value or no value -> "Global" will be unchecked by default (current behaviour)
Sounds to me like this should a property of the installation (app), not the NBM. If there is anything in bin/ or lib/ of course it needs to be global. Otherwise, the NBM itself should not care. If the app wants to forbid user-dir installations, perhaps this should be made possible in some other way.
reassigne to Hrebejk, new owner of autupdate
The autoupdate module automatically defaults to 'Global' if a given nbm installs any file in lib or bin directory. This is fine. But if an nbm has a dependancy on another module that needs to be installed globally (i.e. that installs files in lib or bin dir), then autoupdate module is not correctly detecting this and does not force global update for the dependent (when in fact it should be installed globally). Autoupdate should check the manifest file to see if there is any dependency on lib directory (in addition to checking where the nbm installs files). If this is done, then there will not be a need for module owners to mark an nbm as global specifically and autoupdate itself should be able to correctly identify global modules.
Please explain why when module A has a file in lib/ (say a JAR, I guess?) and module B depends on module A, then B must also be installed globally. IMHO it should not matter where B is. If it needs to refer explicitly to the path of the file in lib/, it can use InstalledFileLocator, as all modules are required to do when referring to file paths in one of the IDE installation directories. Need a concrete example of why this RFE is necessary.
This is also not just about the need to install files to lib or bin directory. Some applications built ontop of NetBeans Platform simply do not want modules to be installed into the users directory. This requirement needs to be enforced (or atleast recommended/defaulted) from the auto update centre. (What Jesse hints at above making the client unable to install userdir modules would be an idea solution for the Minex application. But I suspect other applications might want to have a recommendation, or global default only on the bin and lib binary installing modules...)
I don't like very much the idea of forcing 'global' on the user. On Unix world and many other setups the IDE is installed by the admin on a read-only location. Forced global autoupdate is useless in those cases.
"Forced global autoupdate is useless in those cases." This could indeed be desired, only the person (the system administrator) that installed the NetBeans plaftform application can install extra modules, if permissions are so set.
reassigne to Jirka - new owner of autoupdate
*** This issue has been marked as a duplicate of 54042 ***
verified or just very old