Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[dash-dev] Re: Athena builds that depend on 3rd party plugins (eg., from Orbit or Mozilla)

It uses p2.director. Here's a link to the actual code:

http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.dash/athena/org.eclipse.dash.commonbuilder/org.eclipse.dash.common.releng/tools/scripts/buildAllHelper.xml?view=annotate&root=Technology_Project

(search for "run.director" on line 907; actual <exec> is on line 1023)

N

Jacek Pospychala wrote:
btw. Nick,
how does it work? Do you use p2 director or any other p2 magic to install single plug-in?

thanks
Jacek


Nick Boldt wrote:
I just added a new feature to Athena tonight [1] which you might like.

In the past you could only use "featureIDsToInstall" to grab features from a p2 repo update site; now you can now install individual plugins (eg., off an Orbit site!) too using "pluginIDsToInstall" [2].

So, when configuring your build's dependencies, you can now do this:

dependencyURLs=http://download.eclipse.org/eclipse/downloads/drops/R-3.5-200906111540/eclipse-SDK-3.5-linux-gtk.tar.gz,<more.zips.here> repositoryURLs=http://download.eclipse.org/tools/orbit/downloads/drops/R20090825191606/updateSite,<more.sites.here>
featureIDsToInstall=org.eclipse.gef+org.eclipse.emf+<more.features.here>
pluginIDsToInstall=org.apache.xml.resolver+javax.xml+org.apache.xml.serializer+org.apache.xerces+org.apache.xalan+<more.plugins.here>

[1]http://wiki.eclipse.org/Athena_Progress_Report#2009-09-01
[2]http://wiki.eclipse.org/Common_Build_Infrastructure/Defining_Binary_Dependencies




--
Nick Boldt :: http://nick.divbyzero.com
Release Engineer :: Eclipse Modeling & Dash Athena


Back to the top