In case of a respin we would definitely
include that fix.
Fred Bricon <fbricon@xxxxxxxxx> To:
Cross project issues
06.10.2017 14:30 Subject:
Fw: Xtext is broken in Oxygen 1a Sent by:
While we're on the subject of respinning RC2, JDT has
a critical bug that prevents any project with multiple output folders
(Maven, Gradle) from running any class (be it main or test) from the IDE,
with Java 9. A simple fix was committed yesterday in master, I strongly
believe this should be backported to Oxygen.1a, given that, most likely,
all new greenfield Java 9 projects will use a build tool affected by that
On Fri, Oct 6, 2017 at 8:24 AM, Aleksandar Kurtakov <akurtako@xxxxxxxxxx>
wrote: On Fri, Oct 6, 2017 at 3:15 PM, Daniel Megert <daniel_megert@xxxxxxxxxx>
wrote: > Dear Eclipse PMC > > Should we consider to bring back the internal method and ask for a
respin? > We could provide a fix earlier than Wednesday, but it can also be
risky to > respin the Platform/JDT at this point,.
While the "practical me" would say "Yes, if JDT team feels
comfortable with that", I'm leaning towards -1 for this one because it practically means treating internals as API thus encouraging people to use them directly instead of working close with projects they depend on to make APIs stronger and more feature full. I would +1 a case where the method is bringed back in Oxygen only for the sake of preserving some compatibility.