As part of the PDE
Plugin/Feature export step for a plugin that is NOT using custom build, a
build.xml file is created that has explicit classpath entries to plugin
bundles. For example, my dependency might be org.eclipse.osgi and when the
plugin is built, build.xml contains either a relative path
../../plugins/org.eclipse.osgi_1.0.0.jar or when the PDE target is on a
different drive something like C:\target\eclipse\plugins.
Normally having this hidden
from the user is perfectly OK, except when a Custom Build is used. What I'd
like to be able to do is to specify in my custom build file a classpath such as
${baseLocation}/plugins/org.eclipse.osgi_1.0.0.jar. At this point, I can find
no way via Ant properties to ascertain how I could resolve "baseLocation".
Is there some other property that Custom Build Files should be using? Is this
what the new "pluginPath" property introduced into GenericTargets.xml
in release (3.2?) is purposed for?
If not, might I suggest that
this be added?
TIA
Lyndel McGee