[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- From: Scott Lewis <slewis@xxxxxxxxxxxxx>
- Date: Tue, 05 Oct 2010 05:38:15 -0700
- Delivered-to: firstname.lastname@example.org
- User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:126.96.36.199) Gecko/20100915 Thunderbird/3.1.4
On 10/5/2010 2:46 AM, Markus Alexander Kuppe wrote:
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.
However, now a bunch of unit tests are failing. Who is going to investigate?
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.