Re: [ecf-dev] Please do not change .launch configs used by automated tes

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

Re: [ecf-dev] Please do not change .launch configs used by automated testing

From: Markus Alexander Kuppe <ecf-dev_eclipse.org@xxxxxxxxxxx>
Date: Sat, 16 Oct 2010 13:36:54 +0200
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 (X11; U; Linux x86_64; en-US; rv:1.9.2.9) Gecko/20100922 Lightning/1.0b2 Thunderbird/3.1.4

On 10/16/2010 01:28 PM, Scott Lewis wrote:
>  This makes it difficult to use these launch configs for local testing. 
> Why is it necessary to make the list of bundles 'all in workspace'?

E.g. your launch config might end up being platform dependent
(fragments...). Thus I have found that it's easier to include all
bundles materialized by Bucky.
Locally I usually adapt the launch config, but never push it.

References:
- [ecf-dev] Please do not change .launch configs used by automated testing
  - From: Markus Alexander Kuppe
- Re: [ecf-dev] Please do not change .launch configs used by automated testing
  - From: Scott Lewis

Prev by Date: Re: [ecf-dev] Please do not change .launch configs used by automated testing
Next by Date: [ecf-dev] struggles with egit/git
Previous by thread: Re: [ecf-dev] Please do not change .launch configs used by automated testing
Next by thread: [ecf-dev] struggles with egit/git
Index(es):
- Date
- Thread

Breadcrumbs