[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- From: Markus Alexander Kuppe <ecf-dev_eclipse.org@xxxxxxxxxxx>
- Date: Sat, 02 Oct 2010 14:17:48 +0200
- Delivered-to: firstname.lastname@example.org
- User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:22.214.171.124) Gecko/20100915 Lightning/1.0b1 Thunderbird/3.0.8
On 10/02/2010 08:56 AM, Markus Alexander Kuppe wrote:
> On 10/02/2010 01:02 AM, Scott Lewis wrote:
>> Yes, I understand that this the typical case (requires in features being
>> same as target platform)...but you are also right that they are distinct
>> things...that is, the required plugins in feature.xml end up being in
>> the p2 metadata...and that's why I don't really want to have the
>> requires be used to set the target platform for compile/build. An
>> example of why this doesn't work very well for edge cases is optional
>> bundle dependencies...they shouldn't be in requires (for target
>> platform), but they *do* need to be present for the compiler.
> That's why optional bundles go into the buckminster.cspex of the feature
> and not into requires. But org.eclipse.ecf.remoteservices is not an
> optional dependency for jms.
The build has been fixed  by adding a buckminster.cpsex.