[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [tycho-user] p2 target definition - dependency hell
|
On Tue, Apr 17, 2012 at 2:26 PM, Barrie Treloar <baerrach@xxxxxxxxx> wrote:
> Am I missing the easy way?
Yes there is an easy way.
After looking at the ITs for another problem I saw a target platform like:
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<?pde version="3.5"?>
<target name="eclipse 3.6.0">
<locations>
<location includeAllPlatforms="false" includeMode="planner"
type="InstallableUnit">
<unit id="org.eclipse.rcp.feature.group"
version="3.6.0.v20100519-9OArFKvFtsd7WLUKh-DcYTS" />
<unit id="org.eclipse.equinox.executable.feature.group"
version="3.4.0.v20100524-7M7K-FIhIez-egBko15H73" />
<repository location="http://download.eclipse.org/releases/helios/"; />
</location>
</locations>
</target>
I was fairly sure I gave using *.feature.group a go, not sure what
went wrong the first time.
I also set the versions to 0.0.0 since I dont care about the version
being used, whatever is in the p2 repository is the one to build
against.
My RCP app is pretty slim so with just those two features I get all
the plugins I need to build.
