Community
Participate
Working Groups
I receive the following error during export of a plug-in with Bundle-RequiredExecutionEnvironment: JavaSE-11 Processing inclusion from feature org.eclipse.pde.container.feature: Bundle com.example.e4.rcp_1.0.0.qualifier failed to resolve.: Missing Constraint: Bundle-RequiredExecutionEnvironment: JavaSE-11 Host plug-in JavaSE_0.0.0 has not been found. To reproduce: 1.) Create e4 RCP application with sample data based on the Eclipse 4 RCP application template using execution environment of Java 11 2.) Export product
Vikas, please have a look
I think it is similar to https://bugs.eclipse.org/bugs/show_bug.cgi?id=525280 Right now, export of Plugin projects work fine but not RCP application.
*** This bug has been marked as a duplicate of bug 525280 ***
I don't think the duplicate is correct. I'm having the same issue. Migrated Plugins to BREE JavaSE-11. P2 Director now fails to export the product, as the default (and maximum supported) profile according to JREAction (P2) and profile.list (org.eclipse.osgi) is JavaSE-9. Aaaand again a blocker on the road to Java 11 :( More related to this would be https://bugs.eclipse.org/bugs/show_bug.cgi?id=530150 and https://bugs.eclipse.org/bugs/show_bug.cgi?id=530093, I think.
I managed to work around by providing this p2.inf next to the .product file: provides.1.namespace = osgi.ee provides.1.name = JavaSE provides.1.version = 10.0.0 provides.2.namespace = osgi.ee provides.2.name = JavaSE provides.2.version = 11.0.0
Exports fails with: /home/vogella/workspace/eclipse4book/.metadata/.plugins/org.eclipse.pde.core/temp/org.eclipse.pde.container.feature/package.org.eclipse.pde.container.feature.linux.gtk.x86_64.xml:89: The following error occurred while executing this line: /home/vogella/workspace/eclipse4book/.metadata/.plugins/org.eclipse.pde.core/temp/org.eclipse.pde.container.feature/package.org.eclipse.pde.container.feature.linux.gtk.x86_64.xml:495: The following error occurred while executing this line: /home/vogella/dev/eclipse-2020-06-21/eclipse/plugins/org.eclipse.pde.build_3.10.800.v20200410-1419/scripts/genericTargets.xml:240: A problem occured while invoking the director. The following error occurred while executing this line: /home/vogella/workspace/eclipse4book/.metadata/.plugins/org.eclipse.pde.core/temp/org.eclipse.pde.container.feature/package.org.eclipse.pde.container.feature.linux.gtk.x86_64.xml:495: The following error occurred while executing this line: /home/vogella/dev/eclipse-2020-06-21/eclipse/plugins/org.eclipse.pde.build_3.10.800.v20200410-1419/scripts/genericTargets.xml:240: A problem occured while invoking the director.
I think this issue is caused by JREAction not being able to create the usual a.jre.javase units. The JREAction is stuck in the pre Java 11/modular world. It could be improved to at least generate (with some warning) an IU for the current runtime, for which Equinox can give all interesting information. One workaround can be to include JustJ runtimes in the .product. It comes with installable units that would satisfy the requirement.
*** Bug 567394 has been marked as a duplicate of this bug. ***
*** Bug 568051 has been marked as a duplicate of this bug. ***
*** Bug 568388 has been marked as a duplicate of this bug. ***
In regard to Bug 567394. In that case the there is no problem with export. The problem is that the exported product fails to run even though it runs fine in the Workbench. I also have another Java 11 product that both exports and runs when exported, so it is more than just Java 11. It thus doesn't seem to be the same issue as here. I'll let you decide.
I am trying to apply the 'workaround' listed in the linked bug regarding p2.inf. If it works, I will post here. If it doesn't, I fear we are still stuck. However, we are also beginning to look at using Tycho to drive our product build, which might allow us to adopt Eclipse 4.17 at the same time, and not hit this bug.
(In reply to Eddie Galvez from comment #12) > I am trying to apply the 'workaround' listed in the linked bug regarding > p2.inf. If it works, I will post here. If it doesn't, I fear we are still > stuck. > > However, we are also beginning to look at using Tycho to drive our product > build, which might allow us to adopt Eclipse 4.17 at the same time, and not > hit this bug. oops this was meant for 568051
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
