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 reported several issues with the plugin manager UI yesterday in 102289, but forgot this one. With the old UPdate center UI, I always (after testing locally) installed all modules globally. I am a developer, but I am also the 'Tools Admin' for my group, and I maintain the shared network installations of our compiler, JDK's and tools like NetBeans and Java Studio. My use model is as follows: 1) quit Netbeans, 2) rename my userdir. 3) restart with a fresh userdir 4) download and install module 5) play with it, to test it. 6) quit netbeans 7) put userdir back. If I liked the module, I then download it again and install it globally for all my developers to use, and I send an email out announcing it and how to use it. With the new UI I can't figure out: 1) where are the modules being installed? 2) how do I control where they are installed? I like the new 'uninstall' feature. I wish it would eliminate the need to test modules in a new userdir, but since I don't think, when I uninstall an updated version of a module, that it will reinstall the older version (will it?) I think I'll still have to keep testing in a clean userdir. One other thing that would be nice would be to be able to 'promote' or 'push' a module from the userdir to the netbeans installdir. If the choice of where to install modules was removed to not confuse users who either don't have permissions to the installdir, then maybe the option could be hidden if the user doesn't have the permissions?
Once again I forgot to say I found this in the 6.0 Dev 20060426 build.
I see but it's a use-case what is none of use-cases supported by Plugin Manager. Use-case like this will be covered by a admin console allows to install chosen plugins to install directory, this console not delivered yet. But definitely, this use-case should supported in some way in NB6.
An Admin console works for me. Until then, if it's easier for you, 1 check box to install *all* modules for this instlal session in the install dir would work for me. I don't need the old UI where I could pick and choose the directory for each module. I'd just run the install twice.
> Until then, if it's easier for you, 1 check box to install *all* modules > for this install session in the install dir would work for me. A checkbox for "global installation" will be added either to the Settings tab or to the installation wizard. Settings tab is a good place to hide this option from the regular users, on the other hand even the advanced users who need this might not look for it at Settings tab. Both these pros and cons have to be considered.
I have also use case that requires ability to install plugins globally. I maintain NetBeans installations at our university and I want to provide completely ready to work environment to our students. Therefore I need to install all plugins (like maven support) into global installation directory.
ditto. We have two types of installation: user and server. A server installation needs global updates.
Needs UI spec. how to present in UI
*** Issue 102466 has been marked as a duplicate of this issue. ***
It's appropriate to plugin manager subcomponent.
Fixed in M10. User: rmatous Date: 2007/06/12 02:49:01 Modified: autoupdate/ui/src/org/netbeans/modules/autoupdate/ui/Utilities.java autoupdate/ui/src/org/netbeans/modules/autoupdate/ui/SettingsTab.java autoupdate/ui/src/org/netbeans/modules/autoupdate/ui/SettingsTab.form autoupdate/services/src/org/netbeans/modules/autoupdate/services/InstallSupportImpl.java autoupdate/services/src/org/netbeans/modules/autoupdate/services/InstallManager.java autoupdate/services/src/org/netbeans/api/autoupdate/InstallSupport.java autoupdate/ui/src/org/netbeans/modules/autoupdate/ui/wizards/InstallStep.java
*** Issue 33751 has been marked as a duplicate of this issue. ***
*** Issue 64951 has been marked as a duplicate of this issue. ***