|Re: How to configure a reader to read from a target platform directory [message #723925]
||Fri, 09 September 2011 17:11
| Thomas Hallgren
Registered: July 2009
On 2011-09-09 23:07, Lothar Werzinger wrote:|
> Thomas Hallgren wrote on Fri, 09 September 2011 13:46
>> Hi Lothar,
>> Why would you ever want to read from a target platform rather than from a p2 repository?
>> - thomas
> When I create my initial TP it goes forth to multiple p2 sites to gather what I want for my single sourced application.
> That TP is great, except that I need to exclude certain plugins for either the RAP or RCP builds.
> So what I want to do is to create these subset TPs. However I don't want to go and download all the stuff again from the
> p2 sites and rather use what was materialized in the full TP earlier.
I would strongly suggest that you use the b3 aggregator for this and create a p2 repository which is an aggregation that
contains what's needed. Then you can use that as input to all your builds instead of a TP. IMO, a TP should be viewed as
a black-boxed build artifact. The plugins that it contains are often unpacked (directories) and it's features are always
unpacked. Further more, there's no meta-data.
Powered by FUDForum
. Page generated in 0.01468 seconds