Beyond the map file to fetch them so they're available at build/test
time, you will also want to set this property in your build.properties
in order to package up the jars into your resulting update site:
packageFeaturesIncludedBinaries=true
(that property turns on the PDE runPackager property)
For more tips, tricks, and news on the development of Athena, see the
N&N page:
http://wiki.eclipse.org/Athena_Progress_Report
On 02/04/2010 08:18 PM, Tom Schindl wrote:
Hi,
UFaceKit is an athena build and includes bundles from orbit in the
update-site.
The map:
--------
https://dev.eclipse.org/svnroot/eclipse/org.eclipse.ufacekit/releng/athena/org.eclipse.ufacekit.releng/maps/all.map
The feature(s):
---------------
(miglayout from orbit)
https://dev.eclipse.org/svnroot/eclipse/org.eclipse.ufacekit/features/org.eclipse.ufacekit.ui.jface.feature/feature.xml
(jxpath from orbit)
https://dev.eclipse.org/svnroot/eclipse/org.eclipse.ufacekit/features/org.eclipse.ufacekit.core.feature/feature.xml
Maybe this helps
Tom
Am 04.02.10 21:52, schrieb Wayne Beaton:
I need three JARs from Orbit in my update site. Athena doesn't seem to
want to put them there, so I'm wondering what magic is required. My
feature.xml lists the Orbit bundles. They're referenced in my map file.
Everything seems to build.
My build scripts are in CVS:
/cvsroot/technology
org.eclipse.epp/releng/org.eclipse.epp.usagedata.releng.athena
Google hasn't been very helpful, I'm afraid. I've tried to locate other
projects doing this, but haven't had any luck. Can somebody give me a
pointer?
Wayne
--
Nick Boldt :: http://nick.divbyzero.com
Release Engineer :: Eclipse Modeling & Dash Athena
_______________________________________________
dash-dev mailing list
dash-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/dash-dev
