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.
A typical autoupdate session for me is: - start autoupdate - wow, lots of new goodies, select them all - select 'global' so the modules are installed in the installation directory - remember I'm not root, exit netbeans, su, start netbeans, etc Now this could be resolved by having netbeans ask for a password and su. Alternatively, there could be an option 'Create an upgrade package' which would create a jar containing all the updates along with a small installer to install them in the netbeans directory. So, my scenario would look like: - start netbeans etc - select the modules I like, and instead of installing them, choose 'create installer' - su -c 'java -jar the.new.installer.jar' For an enterprise setting, this is even more useful. Someone downloads, creates the installer, and distributes it via email; others simply apply it. I am not familiar with the module installation process, but I believe it consists mostly of unpacking jars; if so, the installer should be trivial.
There is already simple solution: just select "Install later" option on the last page of AU wizard, click Finish, exit NB, su, start NB. Then Updater will start (before IDE appears) and updates modules as root.
Ooops, I forgot one step.. so proper steps are: 1. select "Install later" option on the last page of AU wizard 2. click Finish 3. exit NB 4. su 5. MOVE all content of userdir/update/download to installdir/update/download 6. start NB. I hope it can help. Please reopen if needed.
Reopen to mark as duplicate
Marking as duplicate of #12506 - very similar request *** This issue has been marked as a duplicate of 12506 ***