org.eclipse.search has been moved back to Java 8 via https://bugs.eclipse.org/bugs/show_bug.cgi?id=565368
On Mon, Jul 27, 2020 at 2:02 PM Ed Willink <e...@willink.me.uk> wrote: > Hi > > This has now happened and it causes a problem. See [1] > Boring Java 8 builds now fail in non-UI contexts. > > My understanding of the original report was that I would have difficulty > starting the Eclipse UI without Java 11 and I commented that better user > help was desirable. > > I am therefore disappointed to discover that applications using the non-UI > org.eclipse.search fail since the UI is not separated into a separate > bundle. > > As I commented on [2] > > *Seems like moving the whole platform to Java 11 just for Jetty is like > amputating a whole leg just because a toe is gangrenous.* > > Since Java 8 is significantly faster [3], the platform needs to ensure > that its beyond Java 8 issues are isolated, e.g an old Jetty if Java 8, a > new Jetty if Java 11. > > Regards > > Ed Willink > > [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=565555 > [2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=565368 > [3] https://bugs.eclipse.org/bugs/show_bug.cgi?id=565563 > > On 20/03/2020 18:34, Mike Wilson wrote: > > Hello cross project people, > > The Eclipse Project PMC has approved a change to the target environments > for the 2020-09 Eclipse release of the Eclipse Project (that is, our 4.17 > release) to be based on Java 11. This will allow us to include Jetty 10, > when it is available as indicated here: > https://www.eclipse.org/lists/jetty-dev/msg03214.html > > Given that this change has the potential to impact downstream projects, we > are asking for feedback now: please let us know if you believe this will > cause problems for your project. > > Note that we are not asking teams to update the BREE for their components, > and it is fine for components to support earlier versions of Java. This > note is just identifying the version of Java that we will use to > validate the September release, and thus will be the supported version for > the Eclipse SDK. > > thanks, > the Eclipse Project PMC > > > _______________________________________________ > cross-project-issues-dev mailing listcross-project-issues-...@eclipse.org > To unsubscribe from this list, visit > https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev > > > > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> > Virus-free. > www.avast.com > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> > <#m_832610710628085431_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > _______________________________________________ > cross-project-issues-dev mailing list > cross-project-issues-dev@eclipse.org > To unsubscribe from this list, visit > https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev > -- Eclipse Platform project co-lead CEO vogella GmbH Haindaalwisch 17a, 22395 Hamburg Amtsgericht Hamburg: HRB 127058 Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel USt-IdNr.: DE284122352 Fax (040) 5247 6322, Email: lars.vo...@vogella.com, Web: http://www.vogella.com
_______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
