[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- From: Markus Alexander Kuppe <ecf-dev_eclipse.org@xxxxxxxxxxx>
- Date: Fri, 01 Oct 2010 17:34:00 +0200
- Delivered-to: email@example.com
- User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:18.104.22.168) Gecko/20100915 Lightning/1.0b1 Thunderbird/3.0.8
On 10/01/2010 04:09 PM, Scott Lewis wrote:
>> On 09/30/2010 11:02 PM, Scott Lewis wrote:
> <stuff deleted>
>> Does it help to revert the change done to feature.xml?
> I removed the requires section of feature.xml...and that didn't help
> (i.e. still failed:
> The strange thing is the initial compile errors are for
> org.eclipse.ecf.provider.jms...which has always been in the JMS feature.
> It's not finding some ECF plugins for compile.
What I meant was to try the last building feature.xml, not to remove
requires all together. Does tree  build successfully?
> I checked on the build machine, and I can see that the target platform
> path does *not* have all the needed ECF bundles...so I guess this is the
> problem. Missing (e.g.) org.eclipse.ecf.provider,
> org.eclipse.ecf.provider.remoteservice and some others. See below for
> the list of the bundles in
> on ecf2.
> I guess the target platform has to be amended/added to. I can't quite
> understand where the target platform (bundles below) is actually being
> gotten from/created for this build.
The TP is created by Buckminster during the build based on the
feature.xmls, buckminster.cspex, *.mspec, *.cquery's and *.rmaps