I keep a set of different extensions locations in C:\eclipse\extensions (each extension location is in a subdirectory of that directory). (Note: p2 is the “new” way to manage plugins, links is the “old” way to reference plugins outside the eclipse installation directory)
#Eclipse os x location of .link files how to
The following procedure explains how to install plugins into different extension locations and share those extension locations between different eclipse installations using the p2 update manager and link files. P2: how I install plugins in extension locations (from the Eclipse and Java Blog by Michael Scharf blog) To better address your issue, you might find interesting the following article: This extra dropins location can be used from more then one Eclipse installations – so you can use it as a shared dropins (watched directory).įor Bundle Pool, you have here a step by step procedure: You can also use an own extra dropins folder: simply add a parameter into eclipse.ini: 2.= /your_path/e34shared_dropin If you want to defined common plugins, use bundle pools (also introduced here) You should add your plugins in ECLIPSE_HOME/dropins. With dropins, Eclipse tries to install and start as much as it can and you don’t really know what’s going on.Ī Local deployment, as shown in this tutorial, would rather use File → Export → Plug-in Development → Deployable plug-ins and fragments.īut the final destination remains in ECLIPSE_HOME/plugins.If you were using the install UI, you’d be informed of the problems before any changes are made.
![eclipse os x location of .link files eclipse os x location of .link files](https://mcuoneclipse.files.wordpress.com/2014/08/resolved-path-variable-for-linked-file.png)
Any number of things could be getting in the way.
![eclipse os x location of .link files eclipse os x location of .link files](https://www.ericlin.me/wp-content/uploads/2012/09/eclipse-configuration.png)
One of the reasons that Eclipse does not recommend the dropins folder method of installation is that there is no feedback if something goes wrong. As oberlies kindly points out in the comments:Įven though they are still documented (in Kepler 4.3 for instance), this thread adds: