|Corollary to org.eclipse.jst.component.dependency in WTP 1.5 [message #204754]
||Tue, 20 November 2007 15:34
Originally posted by: JKSchneider.gmail.com|
A coworker and I are working on an Ivy dependency management plugin targeted
at RAD7 (Eclipse 3.2.2, WTP 1.5.5). The basic concept is wholly similar to
how the Maven plugin functions in that a classpath container is created to
hold the Ivy-managed dependencies in order that we can check our .classpath
into source control and it is not checked out each time we refresh
The issue at hand is how to add the jars and project references included in
this classpath container to the runtime classpath as well. I see that Rob
Frost did some excellent work for WTP 2.0 in exposing a new classpath
attribute and API for tagging classpath containers among other entries for
the runtime classpath.
I was hoping to reproduce a similar behavior in our plugin to support the
already lagging RAD7.
It appears that the key to Rob Frost's extension point lies in
org.eclipse.jst.j2ee.application.internal.operations.ClassPa thSelection and
Surely there is some other way to add classpath resources to the runtime
classpath without modifying the WTP core. I fail to understand how the J2EE
Module Dependencies mechanism worked prior to WTP 2.0 which would appear to
do what we want.
Any pointers as to how the runtime classpath is modified programatically
would be appreciated.
Powered by FUDForum
. Page generated in 0.13005 seconds