Plugins and features referenced in the *source* map file will only be
fetched / compiled / packaged if they're included in a feature being built.
So, to have them available when building and packaging tests, add them to
your test feature(s).
Or, would you prefer to include them as precompiled binaries? If so, I think
it's time to move PDT to the Athena build system, so you can more easily
manage your dependencies.
(You may recall ages ago I was asked if deps you be set in a properties file
rather than exclusively selected by regular expression from the list of
shared deps. Athena supports that, and therefore adding new binary reqs is
trivial: you just list the URLs and they'll be downloaded and will be
available for use when building or testing. Works with both runtime zips and
update site zips. With Athena, you tell the system what URLs to include, and
it generates Ant variables for those URLs/files dynamically; all you need to
do is check the resulting build.cfg file to see how to reference them in
your buildExtra.xml or testExtra.xml files in order to have them be unpacked
On Sat, Apr 25, 2009 at 12:56 PM, Michael Spector <spektom@xxxxxxxxx> wrote:
I have a question regarding the modeling packaging system. Last week I
was working on refactoring Unit tests into a more appropriate (and
runnable by Eclipse builder) format.
New tests depend on org.apache.commons.lang and
org.eclipse.dltk.core.tests plug-ins. I've added entries for these
plug-ins into pdt-extras.map, but it seems like
it doesn't have any influence on the build process: these plug-ins
cannot be found (see my latest build log:
I'll appreciate if you shed some light on this matter.
Thanks in advance!
Nick Boldt :: JBoss, a division of Red Hat
Productization Lead :: JBoss Tools & Dev Studio
Release Engineer :: Eclipse Modeling & Dash CBI