[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
[pde-build-dev] problem with generated build.xml
|
We are having a problem with our build right now and I think I've
tracked it down to a missing classpath entry in our plugin's build.xml
file that is generated by the PDE stuff.
The MANIFEST.MF file for the plugin has the package listed in the
Require-Bundle section and so I would expect the plugin's build.xml
that is generated to have a <pathelement> node for that required
bundle.
I tried running the build process in the debugger and it isn't clear
to me at all where or how the build classpath is assembled.
When I ran with -debug and captured the output, I did notice a line
saying something like "dropping PATH_TO_BUNDLE\@dot from path as it
doesn't exist" (which is correct) yet the generated build.xml file
still had a line that looked like "<pathelement
path="PATH_TO_BUNDLE/@dot"/>". Is it possible that the wrong element
was dropped? What's the best way of debugging this? Is there a place
that I could dump the classpath list before and after pruning to find
out if my suspicion is correct?
If this isn't the right forum for a question like this, I would
appreciate a pointer in the right direction.
Thanks.