e(fx)clipse 0.9.0 on Kepler with Java 7 - eclipse

is it possible to run the e(fx)clipse sample application on Kepler & Java7 at all ?
I took the steps, descripted in tutorial 4 to integrate the target definition(s)
https://wiki.eclipse.org/Efxclipse/Tutorials/Tutorial4
I tried the all-in-one-eclipse as well as upgrading a common kepler-eclipse with update-site http://download.eclipse.org/efxclipse/updates-released/0.9.0/site
However, the Sample Project JavaFX/Samples/e4 Media Application can not be compiled.
With Target Definition "RCP 3x Platform", all! application dependencies can not be resolved
With Target Definition "Target Platform Feature" a warning comes up, that the target version is newer than my current Eclipse installation. There are no comile errors anymore, but running the app I will get a lot of runtime errors like:
Unresolved requirement: Require-Capability: osgi.ee; filter:="(&(osgi.ee=JavaSE)(version=1.8))"
Did anybody get the sample "e4 Media Application" working ?
My Eclipse: Kepler Service Release 2
My Java: JDK 7u40
============== EDIT ==============
Got it working, thanks to Tom!
Install fresh new Eclipse: http:// www.eclipse.org/downloads/packages/eclipse-rcp-and-rap-developers/keplersr2
Install Xtext 2.5.0, Update-Site: http:// download.eclipse.org/modeling/tmf/xtext/updates/composite/releases
Install e(fx)clipse, Update-Site: http:// download.eclipse.org/efxclipse/updates-released/0.9.0/site
Add new Target Platform, Update-Site: http:// download.eclipse.org/efxclipse/runtime-released/0.9.0/site
Select FX Target -> Target Platform Feature

The nightly runtime site already requires Java8 (see announcement on e(fx)clipse newsrpoup!)
If you want to run it on Java7 you need to use http://download.eclipse.org/efxclipse/runtime-released/0.9.0/Site for the target platform

Related

How to install old version of 'Vaadin Plug-in for Eclipse'?

After I updated 'Vaadin Plug-in for Eclipse' from version 4.1.6 to version 4.1.7 (and Vaadin Designer from 4.6.18 to 4.6.20) something broke.
I started to get constant error when oppened Vaadin design (LitTamplate) java file:
An internal error occurred during: "Requesting Java AST from selection".
'boolean com.ibm.icu.text.UTF16.isSurrogate(char)'
This error does not happen when using Eclipse 2022-12 with Vaadin Plug-in 4.1.7 and Vaadin Designer 4.6.20.
But there is other issues there:
https://github.com/vaadin/designer/issues/2443
I was using Eclipse 2021-12 with 'Vaadin Plug-in for Eclipse' 4.1.6 and 'Vaadin Designer' 4.6.18 before update. Now I can not install old versions back into the Eclipse.
Vaadin plugin guide will always offer only the latest version.
https://vaadin.com/eclipse
It would be nice to have version links for installing older versions.
Something like this:
https://vaadin.com/eclipse/2021-12/plugin/4.1.6/designer/4.6.18

How to use Java11 (Java10) with Eclipse Plugin?

If I specify JavaSE-10 as minimum execution environment in my Eclipse plugin:
I get following errors when starting my plugin as Eclipse Application:
org.osgi.framework.BundleException: Could not resolve module: org.treez.core [597]
Unresolved requirement: Require-Capability: osgi.ee; filter:="(&(osgi.ee=JavaSE)(version=10))"
Unresolved requirement: Require-Bundle: org.treez.javafxd3; visibility:="reexport"
-> Bundle-SymbolicName: org.treez.javafxd3; bundle-version="1.0.0.qualifier"; singleton:="true"
org.treez.javafxd3 [586]
Unresolved requirement: Require-Capability: osgi.ee; filter:="(&(osgi.ee=JavaSE)(version=10))"
at org.eclipse.osgi.container.Module.start(Module.java:444)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1634)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1613)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1585)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1528)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
I checked that
Java10 is reverenced under Installed JREs
10 is selected as compliance level
I use Oxygen.3a Release (4.7.3a) Build id: 20180405-1200
=>Is this a bug in eclipse equinox?
=>What else can I check to resolve this issue?
If I remove JavaSE-10 from the minimum execution environment settings I am able to start the Eclipse Application and the plugin seems to work fine.
When I export the plugin I get following warning:
# 25.04.18, 12:25:40 MESZ
# Eclipse Compiler for Java(TM) v20180330-0919, 3.13.102, Copyright IBM Corp 2000, 2015. All rights reserved.
option -bootclasspath not supported at compliance level 9 and above
When I try to use the plugin after installing it from my update page, I get a ClassNotFoundException:
...
Caused by: java.lang.ClassNotFoundException: org.treez.views.tree.TreeViewPart cannot be found by org.treez.views_1.0.0.201804191641
at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:484)
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:395)
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:387)
at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:150)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:499)
at org.eclipse.osgi.internal.framework.EquinoxBundle.loadClass(EquinoxBundle.java:564)
at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:174)
... 114 more
If I use Java8 everything works fine.
Related questions:
Java 8 & Missing required capability Require-Capability: osgi.ee; filter="(&(osgi.ee=JavaSE)(version=1.8))"
How to set up java 10 in Eclipse Oxygen?
How to add org.eclipse.swt (and other plugin dependencies) as an automatic Java9 module?
It looks like Eclipse OSGi does not support Java SE 10 yet. I downloaded the latest Eclipse Oxygen 4.7.3a and opened plugins/org.eclipse.osgi_3.12.100.v20180210-1608.jar. The last supported profile was JavaSE-9.
So, you have two choices here:
Wait until OSGi officially supports JavaSE-10 profile.
If you really want to write a plugin with Java 10 and you have control over the plugins folder (e.g. you develop an Eclipse RCP application), open the OSGI jar and add a new profile JavaSE-10. To do this, you can copy JavaSE-9.profile to JavaSE-10.profile and fix corresponding lines in the new file. Also, you must add a new line to profile.list.
Since OSGi 4.3, the most appropriate way to specify a minimum Java version is using the Required-Capability header, as in:
Require-Capability: osgi.ee;filter:="(&(osgi.ee=JavaSE)(version>=1.10))"
I have had success fixing the reported error by replacing all occurrences of Bundle-RequiredExecutionEnvironment with the above line. In PDE, you may get a warning on the manifest file, but it can be safely ignored. Product validation and product exports seems to work without issue.
The semantic of the BREE header required that an execution environnement descriptor be provided by the OSGi implementation for each specific release of the JRE. In Equinox, this used to be defined through ".profile" files; these profiles have been supported by Equinox up to JavaSE-9, but it has been announced that Equinox they would no longer provide profiles for newer releases of Java.
The Tycho community has handled this issue on their side by creating their own Java 10 profile, but it can't be used directly from PDE. The P2 community is considering copying Tycho's Java 10 profile, but this has been stalled for a long time. I'm not sure how P2 reacts at present when fed bundles that do not contains the BREE header.
What worked for me as a work around was to
Remove the required version entries from the manifest files and ignore the corresponding warnings
Activate the option "Use class files compiled in the workspace" in the export wizard:
(Therefore I assume that something goes wrong during the compilation step of the export wizard if that option is not applied.)
I used Java 11.0.1 and Eclipse SimRel 2018-09 (plus Java11 support plugin)

m2e extension is not installing in Eclipse Luna

When I am installing the m2e extension, it is giving me below error:
I am using this url to download: http://download.eclipse.org/technology/m2e/releases
Cannot complete the install because one or more required items could not be found.
Software being installed: m2e - Maven Integration for Eclipse (includes Incubating components) 1.6.1.20150625-2338 (org.eclipse.m2e.feature.feature.group 1.6.1.20150625-2338)
Missing requirement: Maven Integration for Eclipse 1.6.0.20150526-2032 (org.eclipse.m2e.core 1.6.0.20150526-2032) requires 'bundle com.google.guava [14.0.1,16.0.0)' but it could not be found
Missing requirement: Maven Integration for Eclipse 1.6.1.20150625-2338 (org.eclipse.m2e.core 1.6.1.20150625-2338) requires 'bundle com.google.guava [14.0.1,16.0.0)' but it could not be found
Cannot satisfy dependency:
From: m2e Marketplace 1.6.1.20150625-2338 (org.eclipse.m2e.discovery 1.6.1.20150625-2338)
To: bundle org.eclipse.m2e.core [1.6.0,1.7.0)
Cannot satisfy dependency:
From: m2e - Maven Integration for Eclipse (includes Incubating components) 1.6.1.20150625-2338 (org.eclipse.m2e.feature.feature.group 1.6.1.20150625-2338)
To: org.eclipse.m2e.discovery [1.6.1.20150625-2338]
Try to use below link:
http://download.eclipse.org/technology/m2e/releases/1.4
You might be using older version of eclipse and trying to install latest version of maven.
What worked for me when installing m2e 1.6.2 into Eclipse 4.2.2 (Luna SR2) was add the Orbit project Guava: Google Core Libraries for Java 15.0 bundle from the Orbit project into Eclipse before installing m2e.
(The install error I initially got said m2e 1.6.2 is looking for the Guava 14 bundle, which I could not locate in any of the recommended Orbit builds, but Guava 15 seems to be working just fine so far, and indeed the Guava 15 bundle is what the Luna SR2 Eclipse IDE for Java Developers uses.)
I used this URL for the Orbit build repository for Luna SR2: http://download.eclipse.org/tools/orbit/downloads/drops/R20150124073747/repository/
This specific link could be unstable over time, or maybe you are reading this because of issues with different versions of Eclipse or m2e, so in those cases it would be a good idea to check the Orbit downloads page to find the right Orbit build for to match your Eclipse release.
For those who are not old Eclipse hands, here is step by step what I did to install the Orbit Guava bundle into Eclipse 4.4.2:
From the Eclipse menu: Help > Install New Software...
Click on the Add button. In the resulting dialog, enter:
Name: Orbit Repository for Eclipse Luna SR2 (4.4.2)
Location: http://download.eclipse.org/tools/orbit/downloads/drops/R20150124073747/repository/
Click OK
Once this repository is added to your Eclipse configuration, the m2e feature installation process will be able to find and install the Guava bundle automatically.
The m2e installation may also want to update other packages, so it is a good idea to have the Eclipse Luna update site available prior to the m2e feature install:
Click the Add button again. In the resulting dialog, enter:
Name: Eclipse Update Site
Location: http://download.eclipse.org/eclipse/updates/4.4
Click OK
It's also worth noting that the m2e 1.6.x release line is included in Mars, while the 1.5.x is included in Luna, so that it might be a more conservative choice to use a 1.5 release rather than a 1.6 release.
I can give you a quick answer : Ignore the error.
Actually I'm not quite sure this is the right solution but at least for me it worked just fine. I'm sharing my case because it might help someone.
While I was installing m2e extension, I met the same error message you met. But I ignored the error and was able to continue installing. And then the installation have finished successfully.
Click and take a look at the image
: Install Remadiation Page
I saw the error when I clicked "show original error ... ". But I think it's OK to choose "Keep my installation ... " and click "Next" to continue

Eclipse : Errors occurred during the build Groovy/Grail Project

I have installed GGTS plugin for eclipse kepler 3.5.1 RELEASE. I created simple grail project. But while building project. Its getting error
Errors occurred during the build.
Errors running builder 'Java Builder' on project 'FirstApp'.
org.codehaus.groovy.runtime.StringGroovyMethods.plus(Ljava/lang/String;Ljava/lang/CharSequence;)Ljava/lang/String;
and if we saw in markers, I found this error
Internal compiler error: java.lang.NoSuchMethodError: org.codehaus.groovy.runtime.StringGroovyMethods.plus(Ljava/lang/String;Ljava/lang/CharSequence;)Ljava/lang/String; at
org.codehaus.groovy.grails.transaction.transform.TransactionalTransform.moveOriginalCodeToNewMethod(TransactionalTransform.groovy:259)
Config.groovy /FirstApp/grails-app/conf line 0 Java Problem
I am using feroda 17. Eclipse Kepler.
We were experiencing the same error today, it turned out that the project created by GGTS had a groovy compiler level of 2.3 but the GGTS plugin only supported up to groovy compiler level 2.1.
The fix was to install the "groovy 2.3 compiler for groovy-eclipse".
The compiler can be found under the "language and support tooling" heading in the extensions browser which is opened by clicking the "IDE extensions" button in the STS dashboard.
Although the compiler states that it will automatically become the default workspace compiler in eclipse this did not happen for us. In fact we needed to set it as the workspace default in "preferrences > groovy > compiler" and then restart eclipse (maybe I restarted twice, cant remember exactly).
we also ended up installing "groovy 2.3 compiler for groovy-eclipse" twice as the first time an eclipse IDE update was installed, I think because our kepler installation was a bit old.
Hope this helps.

Missing bundles in osgi framework

I'm trying to run the region digraph bundle of Equinox in Eclipse IDE. When I run the relevant bundle using start command in OSGi command prompt, I'm getting an error saying
The bundle could not be resolved. Reason: Missing Constraint: Import-Package: org.osgi.framework.hooks.bundle; version="1.0.0". To find out the existing version in the framework, I tried the command p org.osgi.framework.hooks.bundle. The result shows all the bundles in the framework. In that list org.osgi.framework.hooks.bundle is not there. This is the same case for few other bundles such as
org.osgi.framework.hooks.resolver. Any helps about how to fix this issue??
What version of Eclipse are you using?
The org.osgi.framework.hooks.bundle package was added in OSGi Release 4.3, and so you would need a version of Eclipse that supports that, which would be at least Eclipse 3.7 (Indigo).