|Enhancing plugin dependencies classpath container [message #1008360]
||Tue, 12 February 2013 03:00
| Laurent Petit
Registered: December 2010
I'm writing Eclipse plugins.
In certain circumstances, I have to directly embed librairies inside the plugins. For this I successfully use the "runtime classpath" feature which allows me to add the relative path inside my plugin project's directory.
So the "deployed / running" problem is a solved one.
Now I would like to ease the pain in the "development" side of things: when I want to both work on my plugin and on the contents of the library, I have the library as a regular (non OSGi, non Eclipse plugin) java project in the workspace.
This implies that everytime I make a change to the library's content, I need to re-package it and replace it inside my plugin.
What I'd like is to be able, during development, to have a project dependency : my plugin project --- depends on ---> my java library.
I don't want (don't have the possibility) to transform my library project into a plugin/fragment project.
What I would like is something like being able to extend the "Plugin Dependencies" Classpath Container with non-eclipse-plugin projects while developing.
Any help much appreciated,