Re: [ecf-dev] JMS build

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

Re: [ecf-dev] JMS build

From: Scott Lewis <slewis@xxxxxxxxxxxxx>
Date: Tue, 05 Oct 2010 05:38:15 -0700
Delivered-to: ecf-dev@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/ecf-dev>
List-help: <mailto:ecf-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/ecf-dev>, <mailto:ecf-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/options/ecf-dev>, <mailto:ecf-dev-request@eclipse.org?subject=unsubscribe>
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.9) Gecko/20100915 Thunderbird/3.1.4

 On 10/5/2010 2:46 AM, Markus Alexander Kuppe wrote:

<stuff deleted>
Hi,

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 ourbuilder...how is the target platform determined for any particularbuild? It would be nice if somehow we could specify (or at least knowwithout consulting the file system and possibly cleaning the workspace)what versions of which features/plugins were to be used as the targetplatform for any particular build. Perhaps this can already bedone...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 bughttps://bugs.eclipse.org/bugs/show_bug.cgi?id=326866 ...as I believeloopback is used for testing in this case.


Scott

Follow-Ups:
- Re: [ecf-dev] JMS build
  - From: Markus Alexander Kuppe

References:
- [ecf-dev] JMS build
  - From: Scott Lewis
- Re: [ecf-dev] JMS build
  - From: Markus Alexander Kuppe

Prev by Date: Re: [ecf-dev] JMS build
Next by Date: Re: [ecf-dev] JMS build
Previous by thread: Re: [ecf-dev] JMS build
Next by thread: Re: [ecf-dev] JMS build
Index(es):
- Date
- Thread

Breadcrumbs