|Re: Installing Eclipse for use by multiple users in a domain environment [message #1770774 is a reply to message #1770754]
||Thu, 17 August 2017 03:44
| Ed Merks
Registered: July 2009
You can take one of two approaches. |
You can download packages directly from https://www.eclipse.org/downloads/eclipse-packages/ and unzip one of more of those wherever you want (with admin privilege if permissions are a problem). The key is that to the end user, the installation be read-only. Eclipse then automatically created a "surrogate" installation in the user's home folder, nested in the .eclipse folder created there. The user will be able to install additional things locally via the surrogate, without modifying the read-only installation itself.
You can do this with the installer as well (running with admin privilege). But, the installer, by default, uses a shared agent with a shared bundle pool, and that's located, by default, in ~/.p2. You can disable the use of a shared bundle pool via the menu control in the upper right (just toggling the green toggle button). Or you can change the location of the shared agent's bundle pool also via the menu control, bringing up the Bundle Pool Management dialog. So you can create your shared agent with its shared bundle pool at any location where you have write permission (and running with as admin you that have pretty much everywhere/anywhere). So you can co-locate the agent in a sensible location relative to where you're going to create all the installations. As that statement suggests, this is most useful if you are going to create several installations, the advantage being that you could create installations for all the packages and the total impact on disk footprint is the union of all unique bundles and features of all those installations, rather than simply having each installation physically contain it's own complete copy. So all 10 installations might take up only as much space as two would take up without a shared bundle pool.(And of course you download each bundle/feature at most once, rather than once per installation... In any case, the key again is that the installation folder and the shared agent folder be read-only to the end user.
Professional Support: https://www.macromodeling.com/
Powered by FUDForum
. Page generated in 0.02798 seconds