February 24, 2010 by markus.oley@vsa.de
Posted in
Hi,
I like ant4eclipse because it seems to be a simple way to do a headless build for my plugins.
But I have the following problem:
Plugin xyz.ui has a dependency to xyz. This is handled via the MANIFEST.MF-File (Require-bundles).
Now I tried to compile with the following build.xml-snippet
targetplatformid="eclipse.target.platform"
destination="${basedir}/destination" />
Both plugins have a src- and a src-gen-path, which contain the source.
But I get the problem, that the compiler can't resolve classes of xyz(src-gen) while compiling xyz.ui.
If I define a depended plugin in java build path - projects. it works.
Is there somewhere a bug or did I forget some additional things to configure?
Greetings
Markus
Same problem
Sorry to resurrect this so long after it was posted, but I'm looking at about the same issue - we have a core plugin that generates some code into src-gen, and we have a ui plugin that declares a dependency on the core plugin in the MANIFEST.MF file via the Required-bundles (as Markus has described).
Everything runs fine from within eclipse, and I can launch a new eclipse instance to tests these plugins and deploy them to an update site and they work fine for people downloading them. When I try and build the workspace with the buildPlugin task, the core plugin builds fine but the ui plugin fails as if it can't see the classes in the src-gen directory of the core plugin. I just started integrating ant4eclipse today so I'm sure there's something I'm missing, but is there something we have to configure on the build script end to make buildPlugin see those classes?
Example
Could you please try to isolate a small example that illustrates the problem? That would make it much easier to reproduce the problem.
Regards,
Gerd