Eclipse Community Forums: P2 » Dropins Link with $PROJECT

Home » Eclipse Projects » P2 » Dropins Link with $PROJECT_LOC(Sequencing Dropins reconciliation after workspace selection)

Show: Today's Messages :: Show Polls :: Message Navigator

Dropins Link with $PROJECT_LOC [message #1015733]

Fri, 01 March 2013 23:36

Jeff B

Messages: 3
Registered: March 2013

Junior Member

I have been searching for a way to do the following in Helios:

1. Start Eclipse
2. Select a workspace
3. Have P2 reconcile all my eclipse\dropins\*.link locations

The intent is to have Eclipse load the plugins associated with my workspace. So many of the *.link files would point to "path=$PROJECT_LOC/../some_plugin_directory".

The rationale is I want to store the plugins with an eclipse project stored in ClearCase so my our group of developers are using the same set of plugins for project they are importing. So the workflow would be 1) select/create workspace 2) import project 3) restart eclipse 4) select workspace which would load the project's plugins.
I guess, it would be even better if I could place some sort of trigger on the project load...

Any ideas on how to either a) delay the dropins reconciliation or b) perform a second dropins reconciliation after the workspace has been selected?

Thanks

Report message to a moderator

Re: Dropins Link with $PROJECT_LOC [message #1016311 is a reply to message #1015733]

Wed, 06 March 2013 00:06

Jeff B

Messages: 3
Registered: March 2013

Junior Member

Does my question make sense?

Report message to a moderator

Re: Dropins Link with $PROJECT_LOC [message #1017288 is a reply to message #1016311]

Mon, 11 March 2013 13:41

Henrik Lindberg

Messages: 2509
Registered: July 2009

Senior Member

On 2013-06-03 1:06, Jeff B wrote:
> Does my question make sense?

Sort of :-)

I guess that you want everyone to use the same target platform (not that
they run the same version of the IDE based on workspace). If so, then
yes, then the question makes sense.

Secondly, using dropin to do anything is far from ideal, and not a long
term solution as it may be removed. There are many problems with using
dropins as components in a dropin do not have a full set of metadata
compared to when they are installed from a p2 repository. You do not
want to use dropins.

Suggest you take a look at the Buckminster project, and the support
offered to materialize a workspace + target platform (this so all
developers get the same setup). The introductory chapters of the
Buckminster Book (available from Buckminster downloads site at eclipse)
may be of help in understanding how "building and packaging in general"
works in Eclipse.

Hope that helps.
- henrik

Report message to a moderator