The properties in the plugin's build.properties
file are read in Java and used when generating the build script. They
are never directly available as ant properties, so it is not possible to
override them like that.
Note that the export of plugins uses
pde.build under the covers so anything you do for the headless build will
also happen during export.
The exception being custom steps in
the customTargets.xml.
I would suggest using a customBuildCallbacks.xml
file in your plugin to either add or remove the test classes. You
would need to make it conditional on a property that you would set in a
headless build that would not be there for export.
http://help.eclipse.org/help33/index.jsp?topic=/org.eclipse.pde.doc.user/guide/tasks/pde_custom_callbacks.htm
-Andrew
"Per Böckman"
<dev2null@xxxxxxxxx> Sent by: pde-build-dev-bounces@xxxxxxxxxxx
07/03/2007 04:59 AM
Please respond to
"Eclipse PDE Build developers list." <pde-build-dev@xxxxxxxxxxx>
To
pde-build-dev@xxxxxxxxxxx
cc
Subject
[pde-build-dev] Mavenish folder structure
Hi,
I'm trying to build a plugin using a maven-like project structure in eclipse
3.3
Is it possible to override the "source.." property to include
test
classes in the PDE Build?
BR,
Per
_______________________________________________
pde-build-dev mailing list
pde-build-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/pde-build-dev