[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [tycho-user] Target platform composition and/or inheritance
|
Hello Igor,
Thanks for your answer.
Yes, for sure it would be even more useful if PDE supported this (if you could add a target platform as a location...), but, I still think it is interesting to have this feature, since you could define your target platforms with PDE, and add them to your pom.xml (anyway PDE is not aware of the pom)
It seems that changing TargetPlatformConfiguration to have a collection of files for target(s) and changing P2TargetPlatformResolver.addTargetFileContentToTargetPlatform to loop on the targets would be the trivial change you were mentioning.
In for 0.14. ? ;-)
Best regards,
Anthony
Le contenu de ce courriel s'adresse au destinataire seulement. Il contient de l'information pouvant être confidentielle. Vous ne devez ni le copier ni l'utiliser ni le divulguer à qui que ce soit à moins que vous soyez le destinataire ou une personne désignée autorisée. Si vous le receviez par erreur, veuillez nous aviser immédiatement et le détruire.
The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.
From: tycho-user-bounces@xxxxxxxxxxx [mailto:tycho-user-bounces@xxxxxxxxxxx] On Behalf Of Igor Fedorenko
Sent: 27 janvier 2012 20:07
To: tycho-user@xxxxxxxxxxx
Subject: Re: [tycho-user] Target platform composition and/or inheritance
I was under impression this was how .target support was originally implemented, i.e. it was possible to have several .target files for each project, but somehow I don't see any traces of that in the commit history. Odd. In any case, I believe this is a legitimate usecase and is next to trivial to support in Tycho. Unfortunately, PDE only allows single .target file for entire workspace, which makes use of multiple .target files for Tycho projects much less attractive.
--
Regards,
Igor
On 12-01-27 6:03 PM, Dahanne, Anthony wrote:
> Hello all,
> I'm wondering whether it would make sense or not to be able to define
> inheritance or composition of Target Platform definitions, (.target,
> TP) I have currently the following situation :
> My project is a set of bundles and features that uses a target
> platform definition , tp1.target But I also have a product definition
> (.product tycho module), that includes elements from tp1.target, but
> also some artifacts found in other p2 repositories.
> What I currently can do is :
> * create another TP, tp1+other.target that my product module could
> rely on, but I would have to maintain 2 similar TPs (tp1.target and
> tp1+other.target)
> * or pollute tp1.target with stuff only needed by the product
>
> What I would like to do is :
> * specify in my product module 2 TPs : tp1.target, and another one,
> other.target, that Tycho would merge at resolution time :
>
> <configuration>
> <resolver>p2</resolver>
> <targets>
> <target>
> <artifact>
>
> <groupId>group</groupId>
>
> <artifactId>parent</artifactId>
>
> <version>0.0.1-SNAPSHOT</version>
>
> <classifier>tp1</classifier>
> </artifact>
> </target>
> <target>
> <artifact>
>
> <groupId>group</groupId>
>
> <artifactId>product</artifactId>
>
> <version>0.0.1-SNAPSHOT</version>
>
> <classifier>other</classifier>
> </artifact>
> </target>
> </targets>
> </configuration>
>
> * or create a new TP, which inherits from tp1.target and adds some
> locations and references it from my product module
>
> I hope you understand what I actually mean, if my request makes some
> sense, I'd be happy to start working on a patch for solution 1 : merge
> targets.
> Thanks,
> Anthony
>
>
>
>
>
> Le contenu de ce courriel s'adresse au destinataire seulement. Il contient de l'information pouvant être confidentielle. Vous ne devez ni le copier ni l'utiliser ni le divulguer à qui que ce soit à moins que vous soyez le destinataire ou une personne désignée autorisée. Si vous le receviez par erreur, veuillez nous aviser immédiatement et le détruire.
>
> The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.
>
>
> _______________________________________________
> tycho-user mailing list
> tycho-user@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/tycho-user
_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tycho-user
