Michael,
For plugins that are being compiled,
you should expect to see a second classpath entry that contains the version
number:
<pathelement path="${build.result.folder}/../plugin.aaa_1.2.3.4/@dot"/>
The absence of the second entry and
the fact that the path entries don't have ${build.result.folder}
seems to imply that the script
generator did not consider these plugins to be compiled in the same run
as the current plugin.
-Andrew
"Weir, Michael"
<Michael.Weir@xxxxxxxxxx> Sent by: pde-build-dev-bounces@xxxxxxxxxxx
08/14/2007 10:03 AM
Please respond to
"Eclipse PDE Build developers list." <pde-build-dev@xxxxxxxxxxx>
In 3.2 the plugins' generated build.xml files wrote java compiler output
class files to
plugin.xxx/
@dot/...
but now, in 3.3, the build.xml writes them to
plugin.xxx_1.2.3.4/
@dot/...
i.e. to a versioned id.
However, plugins that depend on a previously-built plugin (say
plugin.bbb referencing plugin.aaa) will have the unversioned plugin
directory on the compile classpath:
So the compile fails because it can't find classes from plugin.aaa. At
that point, the directories look like this:
<buildDirectory>/
features/...
plugins/
plugin.aaa/
build.xml -- generated by PDE
plugin.aaa_1.2.3.4/
@dot/... -- .class files from compile
plugin.bbb/
build.xml
plugin.bbb_1.2.3.4/
@dot/...
Any help would be greatly appreciated.
This message may contain privileged and/or confidential
information. If you have received this e-mail in error or are not
the intended recipient, you may not use, copy, disseminate or distribute
it; do not open any attachments, delete it immediately from your system
and notify the sender promptly by e-mail that you have done so. Thank
you.
_______________________________________________
pde-build-dev mailing list
pde-build-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/pde-build-dev