|
Re: e(fx)clipse nightly are based on Luna [message #1239702 is a reply to message #1239459] |
Tue, 04 February 2014 20:48 |
|
Is there any place I can still consume a 0.9.0 build before it has been switched to Luna?
The reason I ask is that my Kepler target is now broken and I do not yet want to update to Luna. I was using the nightly because when I use the version from http://download.eclipse.org/efxclipse/updates-released/0.9.0/site/ in my target, when starting an Eclipse runtime (using -Dosgi.framework.extensions=org.eclipse.fx.osgi ), I get the following exception:
!ENTRY org.eclipse.osgi 4 0 2014-02-04 21:47:03.676
!MESSAGE error loading hook: org.eclipse.fx.osgi.fxloader.FXClassloaderConfigurator
!STACK 0
java.lang.NoClassDefFoundError: org/eclipse/osgi/internal/hookregistry/HookConfigurator
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:800)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:190)
at org.eclipse.osgi.baseadaptor.HookRegistry.loadConfigurators(HookRegistry.java:176)
at org.eclipse.osgi.baseadaptor.HookRegistry.initialize(HookRegistry.java:100)
at org.eclipse.osgi.baseadaptor.BaseAdaptor.<init>(BaseAdaptor.java:98)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
at org.eclipse.core.runtime.adaptor.EclipseStarter.createAdaptor(EclipseStarter.java:738)
at org.eclipse.core.runtime.adaptor.EclipseStarter.startup(EclipseStarter.java:259)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
Caused by: java.lang.ClassNotFoundException: org.eclipse.osgi.internal.hookregistry.HookConfigurator
at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
... 31 more
The nightly version that was available up to Monday did not show this error.
|
|
|
|
|
|
|
|
Re: e(fx)clipse nightly are based on Luna [message #1288610 is a reply to message #1288432] |
Tue, 08 April 2014 18:23 |
Thomas Schindl Messages: 6651 Registered: July 2009 |
Senior Member |
|
|
Hi,
Well first of 0.9.0 also support Java8 so you could still go with it.
On your Luna All-In-One problem can you make sure your Eclipse IDE is
launched using Java8 - see "Nightly Builds of Tooling & Runtime require
JavaSE-8" in this group.
All bundles now require the IDE itself run on Java8. You can find out
which java was used to launch your IDE with Help > About Eclipse SDK >
Installation Details, if it is the wrong java you can force eclipse to
launch with a specific one using -vm %PATH_TO_YOUR_JAVA_EXE%
Tom
On 08.04.14 17:35, Claus Hoeltzcke wrote:
> Hi,
>
> first of all, I am new to JavaFX and e(fx)clipse.
>
> Starting off I tested fx with Kepler, installed 0.9 via the update site
> - all worked perfectly.
>
> Since I need some controls only available in Java 8 (DatePicker ...) I
> tested the "AllInOne" Luna SDK provided here. Probably I did something
> wrong, but I cannot find any FX plugins, e.g. to create a new FX project.
>
> It would be great if you could give me a hint to solve my problem.
>
> Thanks in advance, bye Claus
|
|
|
Re: e(fx)clipse nightly are based on Luna [message #1289205 is a reply to message #1288610] |
Wed, 09 April 2014 06:00 |
Claus Hoeltzcke Messages: 4 Registered: April 2014 |
Junior Member |
|
|
Hi Tom,
thanks for your quick answer.
I know Kepler has the Java8 option, but sooner or later I would switch to Luna anyway - now its sooner.
I did run all with Java8 (jdk-8u20-ea-bin-b05-windows-x64-12_mar_2014). Only with the first startup of Luna a Java7 was used for the project itself, since the previous workspace settings where from Kepler.
Could that be the problem - migrating the Kepler workspace to Luna?
However, as I understand, I should see beyond 'New Project' the option to create a JavaFX project like in Kepler.
There seems also no editor for opening/running the fxbuild file, the way I seen it in Kepler.
In Kepler two libraries where listed in the project tree. The FX lib and the JRE. With Luna I only see the JRE - is that correct?
The 'Installed Software' dialog in Luna lists (looks OK to me):
e(fx)clipse - IDE 1.0.0.201404070704 org.eclipse.fx.ide.feature.feature.group BestSolution.at
e(fx)clipse - IDE - Basic 1.0.0.201404070704 org.eclipse.fx.ide.basic.feature.feature.group BestSolution.at
e(fx)clipse - IDE - Converter 1.0.0.201404070704 org.eclipse.fx.ide.converter.feature.feature.group BestSolution.at
e(fx)clipse - IDE - CSS 1.0.0.201404070704 org.eclipse.fx.ide.css.feature.feature.group BestSolution.at
e(fx)clipse - IDE - FXGraph 1.0.0.201404070704 org.eclipse.fx.ide.fxgraph.feature.feature.group BestSolution.at
e(fx)clipse - IDE - FXML 1.0.0.201404070704 org.eclipse.fx.ide.fxml.feature.feature.group BestSolution.at
e(fx)clipse - IDE - Mobile 1.0.0.201404070704 org.eclipse.fx.ide.mobile.feature.feature.group BestSolution.at
e(fx)clipse - IDE - PDE 1.0.0.201404070704 org.eclipse.fx.ide.pde.feature.feature.group BestSolution.at
e(fx)clipse - IDE - RRobot 1.0.0.201404070704 org.eclipse.fx.ide.rrobot.feature.feature.group BestSolution.at
e(fx)clipse addons - Tooling - RoboVM Integration 1.0.0.201404080103 at.bestsolution.efxclipse.robovm.feature.feature.group BestSolution.at
...
Bye, Claus
PS:
Beyond Eclipse->Window->Preferences there is also a JavaFX settings item missing.
The download was:
eclipse-SDK-4.4M6-win32-x86_64-efx-1.0.0-SNAPSHOT
All 64 bit (JRE + Eclipse SDK)
Starting off on a new workspace did not help - no e(fx)clipse project options.
[Updated on: Wed, 09 April 2014 06:33] Report message to a moderator
|
|
|
Re: e(fx)clipse nightly are based on Luna [message #1289263 is a reply to message #1289205] |
Wed, 09 April 2014 07:09 |
Thomas Schindl Messages: 6651 Registered: July 2009 |
Senior Member |
|
|
Hi,
The workspace settings don't matter which java is used to launch the
IDE. If you don't see the wizards this means that the bundles bringing
JavaFX support to you are not activated.
The only reason this can happen is that you are not launching Eclipse
itself with a JDK8! What does About Eclipse > Installation Details >
Configuration report as "java.version"?
You can also check the state of the bundles using the built-in host
console and typing "ss org.eclipse.fx" if they are only in the installed
state they can not be resolved because of the above reason.
Tom
On 09.04.14 08:00, Claus Hoeltzcke wrote:
> Hi Tom,
>
> thanks for your quick answer.
> I know Kepler has the Java8 option, but sooner or later I would switch
> to Luna anyway - now its sooner.
>
> I did run all with Java8 (jdk-8u20-ea-bin-b05-windows-x64-12_mar_2014).
> Only with the first startup of Luna a Java7 was used for the project
> itself, since the previous workspace settings where from Kepler.
> Could that be the problem - migrating the Kepler workspace to Luna?
>
> However, as I understand, I should see beyond 'New Project' the option
> to create a JavaFX project like in Kepler.
> There seems also no editor for opening/running the fxbuild file, the way
> I seen it in Kepler.
> In Kepler two libraries where listed in the project tree. The FX lib and
> the JRE. With Luna I only see the JRE - is that correct?
>
> The 'Installed Software' dialog in Luna lists (looks OK to me):
> e(fx)clipse - IDE 1.0.0.201404070704
> org.eclipse.fx.ide.feature.feature.group BestSolution.at
> e(fx)clipse - IDE - Basic 1.0.0.201404070704
> org.eclipse.fx.ide.basic.feature.feature.group BestSolution.at
> e(fx)clipse - IDE - Converter 1.0.0.201404070704
> org.eclipse.fx.ide.converter.feature.feature.group BestSolution.at
> e(fx)clipse - IDE - CSS 1.0.0.201404070704
> org.eclipse.fx.ide.css.feature.feature.group BestSolution.at
> e(fx)clipse - IDE - FXGraph 1.0.0.201404070704
> org.eclipse.fx.ide.fxgraph.feature.feature.group BestSolution.at
> e(fx)clipse - IDE - FXML 1.0.0.201404070704
> org.eclipse.fx.ide.fxml.feature.feature.group BestSolution.at
> e(fx)clipse - IDE - Mobile 1.0.0.201404070704
> org.eclipse.fx.ide.mobile.feature.feature.group BestSolution.at
> e(fx)clipse - IDE - PDE 1.0.0.201404070704
> org.eclipse.fx.ide.pde.feature.feature.group BestSolution.at
> e(fx)clipse - IDE - RRobot 1.0.0.201404070704
> org.eclipse.fx.ide.rrobot.feature.feature.group BestSolution.at
> e(fx)clipse addons - Tooling - RoboVM Integration
> 1.0.0.201404080103
> at.bestsolution.efxclipse.robovm.feature.feature.group BestSolution.at
> ..
>
> Bye, Claus
|
|
|
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.05174 seconds