JRE greater than 1.8 #631

OPEN learning portal
Submitted vor 3 Monaten

In my real project I need to use at least Java 11 as the Eclipse Quickstart features have that as a minimum requirement. When I switch the build path, MANIFEST.MF, product and target to use an execution environment of JRE11 the products stop working as below.

  • Hibernate – complains about javax.xml.bind as a missing constraint. I added that bundle to the target and feature.hibernate without resolving the missing constraint.

    <location includeAllPlatforms="false" includeConfigurePhase="true" includeMode="planner"
    includeSource="true" type="InstallableUnit">
    <repository location="https://download.eclipse.org/releases/2018-09"/>
    <unit id="javax.xml" version="0.0.0"/></location>
  • EclipseLink – fails with the exception below that indicates EclipseLink was unable to initialize. This is with the javax.xml.bind in the target and the feature.eclipse.

    java.lang.IllegalArgumentException: No [EntityType] was found for the key class [com.vogella.jpa.model.Todo] in the Metamodel - please verify that the [Entity] class was referenced in persistence.xml using a specific <class>com.vogella.jpa.model.Todo</class> property or a global <exclude-unlisted-classes>false</exclude-unlisted-classes> element.

Can you provide updated configuration that will work with Java 11?


  vor 3 Monaten

Hi Timonthy,

I just updated the e4.client to use Java 11 as minimum and it still works for me with the Eclipse Link product. I pushed the update to the repo, please have a look.

As for Hibernate, I need to check if they offer updated libraries. I try to do this next week.

Best regards, Lars

  vor 3 Monaten


In my attempt, I changed the JRE to 11 for all plugins. You only changed the one with the Application class.

Just to confirm my understanding, shipping my product with at least a JRE 11 will enable any plugin that needs that level to use it but those that need 1.8 will still work. If correct, this is an "aha ha" moment, that all plugins don’t have to use the same JRE and compliance level.

What are the requirements / best practices around setting an Execution Environment at the target and product level when plugins need different levels of JRE?


Please login to write a comment.