[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- From: Markus Alexander Kuppe <ecf-dev_eclipse.org@xxxxxxxxxxx>
- Date: Tue, 05 Oct 2010 14:47:10 +0200
- Delivered-to: firstname.lastname@example.org
- 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/05/2010 02:38 PM, Scott Lewis wrote:
> On 10/5/2010 2:46 AM, Markus Alexander Kuppe wrote:
>> <stuff deleted>
>> I've fixed the JMS build (again). It broke this time due to an outdated
>> target platform (cleaning the workspace fixed the problem).
> This fault brings up the question: with Buckminster and our
> builder...how is the target platform determined for any particular
> build? It would be nice if somehow we could specify (or at least know
> without consulting the file system and possibly cleaning the workspace)
> what versions of which features/plugins were to be used as the target
> platform for any particular build. Perhaps this can already be
> done...but I'm just not aware of how.
We could save Buckminster's Bill of Material (BOM) . Volunteers anybody?
>> However, now a bunch of unit tests are failing. Who is going to
> I will. It seems likely to me that it's related to the change for bug
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=326866 ...as I believe
> loopback is used for testing in this case.
True, in that case the solution is simply to set
"org.eclipse.ecf.osgi.services.discovery.allowLoopbackReference" to true
in the test .launch.