[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 18:55:31 +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/01/2010 06:49 PM, Scott Lewis wrote:
> I don't know....I'll fuss with trying that as soon as I can. I don't
> immediately see how the requires in feature.xml would have anything to
> do with the target platform contents though...and it appears to me that
> target platform contents is the problem here (although I admit I don't
> know why it was working previously).
Well, Bucky needs to know what to put into the TP. Without requires, how
should it know?
> Ok...so I guess I need to know...what are the right additions (to cspex,
> mspec, cquery and/or rmap) to include all of the ECF sdk (some
> successful recent build from HEAD I guess) in the JMS target platform?
> Don't we have some boilerplate for that (i.e. isn't it already like
> that in some other builds)? If so just point me in that direction.
IMO it should not be necessary to change anything except the
feature.xml. The build used to work before the change to feature.xml.