ld get
>>> that up to 1.8, that would be great.
>>>
>>> Nick, what would have to be done to bump up JEE Tools to 1.8?
>>>
>>>
>>> Regards,
>>>
>>> John Collier
>>> Software Developer, WDT/IBM Cloud
>>> Email: jo
>>>
>>>
>>> Regards,
>>>
>>> John Collier
>>> Software Developer, WDT/IBM Cloud
>>> Email: john.j.coll...@ibm.com
>>> Phone: (905)-413-3389 <(905)%20413-3389>
>>>
>>>
>>>
>>>
n.j.coll...@ibm.com
>> Phone: (905)-413-3389 <(905)%20413-3389>
>>
>>
>>
>> From: Nick Boldt
>> To: Nitin Dahyabhai
>> Cc:Keith Chong , Victor Rubezhny <
>> vrube...@redhat.com>, "General discussion of project-wid
dt
> To:Nitin Dahyabhai
> Cc:Keith Chong , Victor Rubezhny <
> vrube...@redhat.com>, "General discussion of project-wide or
> architectural issues."
> Date:2017/12/18 10:57 AM
> Subject:Re: [wtp-dev] Broken SSE builds due to compilat
lds due to compilation error,
but only in Hudson (can't reproduce locally)
Sent by:wtp-dev-boun...@eclipse.org
*wild cheering for dropping support for BREE = J2SE-1.4*
*waves Team Nitin flag*
If you're keen to break some more eggs, please have a look at
https://bugs.eclipse.org/
*wild cheering for dropping support for BREE = J2SE-1.4*
*waves Team Nitin flag*
If you're keen to break some more eggs, please have a look at
https://bugs.eclipse.org/bugs/show_bug.cgi?id=528800 re: updating
toolchains.xml to the latest JDKs, and maybe removing support for obsolete
BREEs like JD
I intend to bump up the BREE of both SSE core and UI to 1.8 in the master
branch to get us past this once and for all. With the platform dependencies
already there, as long as I can keep the code compliance itself where it is
(it's more a pragmatic choice than a dogmatic one) I don't see much ca
I've been seeing this for about a week now:
[ERROR] Failed to execute goal
org.eclipse.tycho:tycho-compiler-plugin:1.0.0:compile
(default-compile) on project org.eclipse.wst.sse.ui: Compilation failure:
Compilation failure:
[ERROR] /jobs/genie.webtools/webtools-sourceediting_R3_10/workspace/
core/
