Re: [tcf-dev] Update TCF build environment to use Eclipse 4.3.1 as targe

["Oberhuber, Martin" <Martin.Oberhuber@xxxxxxxxxxxxx>]

Hi Uwe,

That sounds like a great plan !

I have only one comment : 

middle-term, we might want to use some new API from Eclipse 4.x.  Which means that the downloads area will have to be populated from the 4.x build job at that point. That should be OK under the preconditions that either 

(a) new API is only used in plugin(s) where the 3.x compatibility is not needed , eg new TE functionality, or
(b) plugins using new API have "backward compatibility" where things like MethodNotFoundError are caught and handled, or
(c) we continue building against 3.x and use Java Introspection to drive 4.x API where possible.

Most Eclipse projects that I know do option (b), ie their main development target is 4.x and they add compatibility hacks where needed, which they routinely test with unittests running against 3.x .

So, long story short, let's stick to your plan building against 3.x as the master until the point where we deliberately want to add 4.x API use for any reason.

Thanks,
Martin
--
Martin Oberhuber, SMTS / Product Architect - Development Tools, Wind River
direct +43.662.457915.85  fax +43.662.457915.6


-----Original Message-----
From: tcf-dev-bounces@xxxxxxxxxxx [mailto:tcf-dev-bounces@xxxxxxxxxxx] On Behalf Of Stieber, Uwe
Sent: Friday, January 24, 2014 8:24 AM
To: TCF Development
Subject: Re: [tcf-dev] Update TCF build environment to use Eclipse 4.3.1 as target platform

Hi Eugene,

OK. Current plan is to have two jobs, one building against the Eclipse 4.x and one building against the Eclipse 3.8.2 platform. As the current "tcf-master" job is building just fine, I'll leave that job untouched and let it continue to use Eclipse 3.8.2. Additional to the "tcf-master", I'll create 2 new jobs, "tcf-master-4.3" and "tcf-master-4.4" building against Eclipse 4.3.x (Kepler) and Eclipse 4.4 (Luna). As we had bug reports in the recent past that some API changes in Luna broke the build, I want to have things verified against the released 4.x version and against the development stream. While all jobs provides the org.eclipse.tcf.repo.zip archive for download, only the original "tcf-master" job will update the download area at download.eclipse.org. 

Does this sounds reasonable?

Thanks, Best regards, Uwe :)



> -----Original Message-----
> From: tcf-dev-bounces@xxxxxxxxxxx [mailto:tcf-dev-bounces@xxxxxxxxxxx] 
> On Behalf Of Eugene Tarassov
> Sent: Donnerstag, 23. Jänner 2014 19:29
> To: TCF Development
> Subject: Re: [tcf-dev] Update TCF build environment to use Eclipse 
> 4.3.1 as target platform
> 
> Hi Uwe,
> 
> > Question is: Does anyone still requires that the TCF plug-in's / 
> > features are built against Eclipse 3.8.2
> for compatibility reasons?
> 
> Yes, Xilinx SDK is still based on Eclipse 3.8.2. Could you setup a new 
> Hudson job for Eclipse 4.*? It's OK for us if 3.8.2 build does not include Target Explorer.
> 
> Thanks,
> Eugene
> 
> 
> -----Original Message-----
> From: tcf-dev-bounces@xxxxxxxxxxx [mailto:tcf-dev-bounces@xxxxxxxxxxx] 
> On Behalf Of Stieber, Uwe
> Sent: Thursday, January 23, 2014 1:20 AM
> To: TCF Development
> Subject: [tcf-dev] Update TCF build environment to use Eclipse 4.3.1 
> as target platform
> 
> Hi everyone,
> 
> I'm planning to move the TCF build to use Eclipse 4.3.1 SDK as target 
> platform. Up to now, all TCF plug- in's and features are built against Eclipse 3.8.2 SDK.
> 
> Question is: Does anyone still requires that the TCF plug-in's / 
> features are built against Eclipse 3.8.2 for compatibility reasons?
> 
> Note that there are no plans to change the minium required versions 
> declared by the plug-in's / features, so installing TCF into a Eclipse 3.8.2 environment is still possible, at least for the time being.
> 
> Thanks, Best regards, Uwe :)
> _______________________________________________
> tcf-dev mailing list
> tcf-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/tcf-dev
> 
> 
> 
> This email and any attachments are intended for the sole use of the 
> named recipient(s) and contain(s) confidential information that may be 
> proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments.
> Delete this email message and any attachments immediately.
> 
> 
> _______________________________________________
> tcf-dev mailing list
> tcf-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/tcf-dev
_______________________________________________
tcf-dev mailing list
tcf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tcf-dev