[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [ease-dev] EASE no longer compiles against Oxygen
|
We faced similar issues with the Trace Compass Incubator project:
limited [wo]manpower, wanting to get the latest development features and
still hoping our stuff works with various versions of the main project.
We chose to branch the code whenever the API breaks. In the branches, we
keep a target that points to the stable version. And we build different
update sites for each of those branches. Older versions may not have all
the latest features unless we backport patches (which we haven't really
done yet), but at least they get features that fully work. That workflow
is only a few months old, so our experience is limited, but we used to
have users complain about broken features, we hope not to have that
anymore :D
Cheers,
Geneviève
On 7/16/19 9:06 AM, Christian Pontesegger wrote:
>>
>> Generally building against new stuff and running it on an old
>> framework can lead to nasty runtime problems (missing methods, class
>> hierachy problems). The other way round is normally better.
>> Thats why we build against Oxygen at the moment.
> You are right, the way we build we cannot guarantee things to work on
> older platforms. Then on the other hand sticking to a target platform
> based on Oxygen or similar old platforms blocks us from adding new
> features that depend on newer targets
> (eg the fresh UI builder needs 2019-06)
>
> With the current manpower the decision is to keep the development as
> close as possible to the eclipse release train, possibly sacrificing
> compatibility with older versions.
>
> best regards
> Christian
> _______________________________________________
> ease-dev mailing list
> ease-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/ease-dev
