Re: [tycho-user] How to handle third party libraries?

[Eric Jain <eric.jain@xxxxxxxxx>]

On Thu, Jun 30, 2011 at 09:51, Henrik Niehaus <henrik.niehaus@xxxxxx> wrote:
> Any hints on this are appreciated. Also, if you know a better way to
> achieve my wanted setup, please let me know, how you are doing it.

Instead of having a target platform copy of Eclipse, I just reference
the required features from a .target definition file like so:

<target name="Target Platform">
<locations>
<location includeAllPlatforms="false" includeMode="planner"
type="InstallableUnit">
<unit id="org.eclipse.rcp.feature.group"
version="3.6.2.r362_v20101104-9SAxFMKFkSAqi8axkv1ZjegmiBLY"/>
<repository location="http://download.eclipse.org/eclipse/updates/3.6/"/>
</location>
<location includeAllPlatforms="false" includeMode="planner"
type="InstallableUnit">
<unit id="org.eclipse.contribution.weaving.feature.group"
version="2.1.3.e36x-20110622-1300"/>
<repository location="http://download.eclipse.org/tools/ajdt/36/update"/>
</location>
...
<location path="${project_loc:Target Definition}" type="Directory"/>
</locations>
</target>

Note the last location, which references a project in the workspace
that has a plugins subdirectory containing all the third-party OSGi
bundles that are not available through p2 update sites. Tycho doesn't
support this, so I need to run the FeaturesAndBundlesPublisher on the
build server and maintain a separate target definition that includes a
hard-coded path like so:

<location includeAllPlatforms="false" includeMode="planner"
type="InstallableUnit">
<repository location="file:///var/p2"/>
</location>

I hope to get rid of the FeaturesAndBundlesPublisher step one day, but
for now this works well enough for us.