Eclipse Community Forums: Java Development Tools (JDT) » Compiler compliance: Behind the scenes

Help

Home

Home » Language IDEs » Java Development Tools (JDT) » Compiler compliance: Behind the scenes

Show: Today's Messages :: Show Polls :: Message Navigator

Compiler compliance: Behind the scenes [message #1862712]

Thu, 21 December 2023 23:43

Friedrich Spee von Langenfeld

Messages: 1
Registered: December 2023

Junior Member

It is possible (despite not being a good idea) to choose a Compiler compliance level greater than the highest version offered by the current JRE if the JRE is old (e.g.: Compiler Compliance Java 12, installed JRE 1.8).

I tried to find out how Eclipse finds the entries of the Compiler Compliance dropout menu and generates the GUI dropout list, but failed. The eclipse.platform Git repository contains many .pref and .htm files, but none of these seems to be related to the real source code generating the menu and its entries - many properties, no action. I had expected something like "generate_sublist(currently_known_java_versions, x -> x < core.compiler.compliance) or similar, but I had no luck searching the repository eclipse.platform (hopefully assuming that I have searched within the correct subproject eclipse.platform).

My questions: How does Eclipse generate this specific menu entry and how does it collect the dropout menu items of the property ,,Compiler compliance level"? Where do I have to search? And last but not least: How does Java act during class file generation when confronted with a Compiler Compliance JRE strictly higher than the installed JRE?

Many thanks in advance

Friedrich

Attachment: Eclipse Compiler Compliance.PNG
(Size: 25.48KB, Downloaded 47 times)

Report message to a moderator

Re: Compiler compliance: Behind the scenes [message #1862716 is a reply to message #1862712]

Fri, 22 December 2023 06:56

Ed Merks

Messages: 33264
Registered: July 2009

Senior Member

All direct JDT things come from repositories in this organization:

https://github.com/eclipse-jdt

The Oomph setup is the easiest way to clone all the JDT projects int a workspace free of compiler errors for analysis, for prototyping of changes and for contribution:

https://github.com/eclipse-jdt/.github/blob/main/CONTRIBUTING.md#create-an-eclipse-development-environment

The eclipse-platform also has an Oomph setup:

https://github.com/eclipse-platform/.github/blob/main/CONTRIBUTING.md#creating-an-eclipse-development-environment

That one includes the setups for the Platform (UI and base frameworks) Equinox (OSGi runtime), PDE, and JDT. These are the components that are used to produce the Eclipse Project's Eclipse SDK downloads.

I don't get the impression that anyone on the JDT team spends much time looking at this forum. You could ask questions here instead:

https://github.com/eclipse-jdt/eclipse.jdt.core/discussions

Ed Merks
Professional Support: https://www.macromodeling.com/

Report message to a moderator

Previous Topic:	Using within WSL via Language Serve Protocol (like VS Code does)?
Next Topic:	eclipse launch fails on installing ibm liberty developer tools plugin

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Jan 16 13:00:07 GMT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter