[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [ecf-dev] ECF project and Tycho
- From: Aleksandar Kurtakov <akurtako@xxxxxxxxxx>
- Date: Wed, 5 Nov 2014 07:48:15 -0500 (EST)
- Delivered-to: email@example.com
- Thread-index: IJ/IJlTuYkPPvTbY7cojq+UxdEROnw==
- Thread-topic: ECF project and Tycho
----- Original Message -----
> From: "Markus Alexander Kuppe" <ecf-dev_eclipse.org@xxxxxxxxxxx>
> To: "Eclipse Communication Framework (ECF) developer mailing list." <ecf-dev@xxxxxxxxxxx>
> Sent: Wednesday, November 5, 2014 2:38:03 PM
> Subject: Re: [ecf-dev] ECF project and Tycho
> On 05.11.2014 13:33, Aleksandar Kurtakov wrote:
> > * Anything that you have been looking to improve in the current build
> > so it can be taken in account when working on the tycho build so
> > target the end goal directly?
> what is the advantage of a Tycho based build compared to the current
> Buckminster based one?
First few I think of are:
* being requirement for having ECF being part of Eclipse Foundation Long Term Support program - https://lts.eclipse.org/content/criteria-being-lts-ready
* stigmatization of build procedures - Tycho has become the de-facto standard in Eclipse land and having Tycho build system eases the life of adopters significantly as there is only one build system to deal with for people always building from source or doing their own aggregation builds for products.
These are not technical benefits(I stay away of it on purpose for now) as in my eyes making life easier for adopters is way more important than some small technical benefit/negative.
Red Hat Eclipse team
> ecf-dev mailing list
> To change your delivery options, retrieve your password, or unsubscribe from
> this list, visit