Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tycho-user] .target hierarchies


One question about your usage pattern.
The help shows a pom.xml which can generate the .target from a tpd.
what is the usecase for this? (To do it in the build cycle I mean).

Thanks for this great tool, using it already!
Cheers Christophe

On Wed, Aug 6, 2014 at 1:25 PM, Christophe Bouhier <dzonekl@xxxxxxxxx> wrote:
Merci Pierre-Charles!
Spot-on, exactly what I need.
rgds Christophe
p.s. Ironic, we need DSL's to generate DSL's. (Which .a target is).

On Wed, Aug 6, 2014 at 12:05 PM, Pierre-Charles David <pierre-charles.david@xxxxxxx> wrote:
Le 06/08/2014 11:43, Christophe Bouhier a écrit :

I find myself repeating P2 repository locations in various target files. Is there a way in tycho add multiple target files? (Which would be merged), Ideally a target hierarchy would be nice to have.

I don't think it is possible with .target files themselves, but you can have a look at [1] which provides a higher-level textual DSL to define your target platforms, and which supports reuse/inclusion of commonly used parts. The source files in the DSL can generate fully-resolved .target files usable both inside Eclipse and by Tycho.

We use it extensively in Sirius [2] and even publish the target definitions as part of our build at [3] (click on "Show directory contents." to see the files). The DSL can resolve target definitions accessible through http, so a downstream project can add a line like this in its target definition and reuse the exact definition used by Sirius itself with zero duplication:

include ""


tycho-user mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

Back to the top