| Re: [cdt-dev] CDT-8.4 requires Eclipse 4.x ... CDT-8.3.x maintenance ? |
|
It's really hard to imagine how any bug fixing on 8.3 would introduce 4.x dependencies. I've lost the drive and motivation to do an official 8.3.1 release. So unless someone else
does, it's even harder to imagine it breaking if doesn't change.
:D From: cdt-dev-bounces@xxxxxxxxxxx [cdt-dev-bounces@xxxxxxxxxxx] on behalf of Oberhuber, Martin [Martin.Oberhuber@xxxxxxxxxxxxx]
Sent: Wednesday, May 28, 2014 9:58 AM To: CDT General developers list. Subject: Re: [cdt-dev] CDT-8.4 requires Eclipse 4.x ... CDT-8.3.x maintenance ? Right, building against 8.4 should still support running on 8.3; But I’m going to lose the confidence that nobody accidentally breaks cdt-8.3 / eclipse-3.8.2 compatibility which is a must-have for tcf-1.2 .
I’m not yet sure where I’ll go with this… but tentatively it sounds like I’ll need a cdt-8.4/luna main build along with a cdt-8.3/e382 verification build where the latter doesn’t build terminal. I don’t know yet how to conditionally disable a module in maven. Will see where that gets us.
Thanks, Martin -- Martin Oberhuber, SMTS / Product Owner – Development Tools, Wind River direct +43.662.457915.85 fax +43.662.457915.6
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
On Behalf Of Doug Schaefer
It's not clear how building against the CDT 8.4 repo forces TCF to run against CDT 8.4. If we're API compliant like we promise you should be able to run TCF against 8.3 as well even
though it's built against 8.4.
From:
cdt-dev-bounces@xxxxxxxxxxx [cdt-dev-bounces@xxxxxxxxxxx] on behalf of Oberhuber, Martin [Martin.Oberhuber@xxxxxxxxxxxxx] Hi Doug,
Thanks for all your efforts on the natives feature.
My current problem with Terminal is more of a build problem … the TCF build as a whole has to run against one CDT repo as a whole (and TCF-Debug uses CDT-Debug which uses CDT-UI). Thus the TCF build (as a whole) can’t run on Eclipse 3.8 any more at the moment, and I’m afraid that’s a blocker for me … but the problem is very new and I’m looking for clever solutions. Backporting the natives feature to the CDT-8.3.x was one of the ideas that I had entertained… but that is too early to call a plan.
Anyways, let’s hear from other people as you suggested.
Shall CDT forcefully break Eclipse 3.8 compatibility to force people update even if there’s no technical reason ? Or shall it just announce “no more 3.8 support in Luna” but take a relaxed approach and not break it as long as it’s not in the way ?
Thanks, Martin -- Martin Oberhuber, SMTS / Product Owner – Development Tools, Wind River direct +43.662.457915.85 fax +43.662.457915.6
From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
On Behalf Of Doug Schaefer
Have we not done enough with the natives feature to satisfy the terminal view? I thought we had. It's only the cdt.ui plug-in that depends on e4. You shouldn't be affected.
From:
cdt-dev-bounces@xxxxxxxxxxx [cdt-dev-bounces@xxxxxxxxxxx] on behalf of Oberhuber, Martin [Martin.Oberhuber@xxxxxxxxxxxxx] Hi Doug,
I mostly agree with you : there needs to be a path forward for modernization.
So I’m absolutely in favor of adding an item to the Release Review documentation (or download pages or whatever) explicitly stating “CDT 8.4 requires Eclipse 4.3.2 or newer” or something similar. We clearly don’t want the CDT to be stuck or the 3.x support to be an impediment of any sort ; and we want to clearly communicate that. Luna as a yearly major release is a good time for officially announcing EOL for 3.x support.
Now that being said, I don’t quite understand why you want to forcefully and deliberately break 3.x when there is no technical reason.
My current use-case is this: Community member has Eclipse 3.8 and wants to install the Local Terminal from the marketplace. Local Terminal requires cdt-8.4 because I need my contribution from bug 303083. è Community member is probably pissed thinking “why should I update to Eclipse 4.x just for a simple app like the terminal”.
I really appreciate the effort that Marc-Andre has made and I’d love to see this being accepted … “as long as it’s easy to do and doesn’t stand in the way of innovation” as we said in Reston 2013. Plus, clear communication NOW that there’s NO PROMISE whatsoever for the Luna SR cycle.
Does that sound acceptable ? Shall we wait for other committer’s comments ?
Thanks, Martin -- Martin Oberhuber, SMTS / Product Owner – Development Tools, Wind River direct +43.662.457915.85 fax +43.662.457915.6
From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
On Behalf Of Doug Schaefer
I think you were in the room. At the CDT summit in Reston in 2013, we promised one more release of 3.8 compatibility and that's it. That was Kepler.
From:
cdt-dev-bounces@xxxxxxxxxxx [cdt-dev-bounces@xxxxxxxxxxx] on behalf of Oberhuber, Martin [Martin.Oberhuber@xxxxxxxxxxxxx] Hi all,
While CDT-8.3 could work on Eclipse 3.8.2 it seems that CDT-8.4 now requires Eclipse 4.x (some CSS dependency in o.e.cdt.ui).
I seem to have missed the discussion where this was agreed on. For some in the community, this might be a very relevant thing to know; So if some discussion has happened, can you point me to it ? And make sure it gets mentioned in the Luna Release Review.
TCF-1.2 for instance is designed to still run on Eclipse 3.8.2 , that’s what we agreed with some of our adopters; therefore we can only depend on CDT-8.3 and none of the newer API’s (like bug 303083 – sigh – trying to find a solution here). We are of course contributing to Luna and testing against Eclipse-4.4 / CDT-8.4 but we’re building against CDT-8.3 and the old API’s only.
I see some maintenance still ongoing in the cdt_8_3 branch: http://git.eclipse.org/c/cdt/org.eclipse.cdt.git/log/?h=cdt_8_3 Could the CDT committers consider a CDT 8.3.1 maintenance release for those stuck on Eclipse 3.8.2 at some point ?
Thanks, Martin -- Martin Oberhuber, SMTS / Product Owner – Development Tools, Wind River direct +43.662.457915.85 fax +43.662.457915.6
|