|Get something similar to bundleClasspathResolvers for development/compilation-time [message #740306]
||Tue, 18 October 2011 11:15
| Thomas Schindl
Registered: July 2009
In 3.8 M2 bundleClasspathResolvers was added to allow dynamic
contribution of classpath information when launching.
My problem is not the runtime look up of bundles because I use
Equinox-Adaptor-Hooks. My current problem is the compile time because
PDE naturally has no idea what's going on at runtime.
The work-around I used until now was to point jars.extra.classpath to
the library but this has 2 problems:
* No JavaDoc is displayed and hence e.g. argument names are arg0, ...
* The location is hard coded
I think in fact i have 2 problems (which jars.extra.classpath address both):
a) Development-Time: I need to make RequiredPluginsClasspathContainer
cleverer so that it can dynamically locate the
b) Export-Time: I need to make the export system add the external jar
when compiling (the same problem I'm going to face with
To solve a) I hacked the RequiredPluginsClasspathContainer so that it
adds the extra jar if it encounters counters my special bundle and so
package imports, ... are working.
On b) I have no clue yet how this could be addressed I tried to navigate
through the PluginExportOperation but don't get how the compile path is
I think if I can address b) I could come up with an extension point to
PDE which allows one to make PDE aware of things one can do with
Any one any pointers ideas?
Powered by FUDForum
. Page generated in 0.19454 seconds