OlivierLagneau
|
Posted: January 12, 2010 21:49 by OlivierLagneau
|
|
Interesting remarks and questions are already raising up. Here are some Thanks a lot for this feedback ! On behalf of tbee who provided feedback on his experience using the NetBeans project import feature of plugin 1.2.1, here is what he reports on the blog of Jonathan Giles. see comments on the JavaFX 1.2.1 Plugin for Eclipse Released! post on Jonathan's blog. Here it is : I tested the Sun plugin against JFXtras and this is what I came up with: - import netbeans project does not use the same build path (build/bin instead of build/compiled) - import netbeans project does correctly handle \jfxtras-common \${platforms.default_fx_platform.lib}\jre\lib - you cannot specify which JavaFX to use (Exadel’s allow to specify the combination) - you need to manually include deploy.jar and javaws.jar from the java (jdk/jre) lib in the project or in the used installed JRE - Java classes are not correctly imported in JFX classes (XDialog uses DialogStage but there is an error: “cannot find symbol symbol : class DialogStage location: class org.jfxtras.stage.XDialog”) DialogStage is compiled. - in the package explorer packages with just JFX classes are visually shown as empty (map icon is white, not orange) - after include deploy.jar and javaws.jar to the used Installed JRE, they are not present in the runtime path - C:\Documents and Settings\User\My Documents\NetBeansProjects\jfxtras\common\src\org\jfxtras\app\XLauncherEnvironment.java:30: package com.sun.deploy does not exist import com.sun.deploy.Environment; And that last one kinda block any furhter testing. |
Some issues importing existing NetBeans projects into Eclipse plugin 1.2.1
4 posts
Replies: 3 - Last Post: January 23, 2010 18:03
by: OlivierLagneau
by: OlivierLagneau
showing 1 - 4 of 4
|
OlivierLagneau
|
Posted: January 12, 2010 22:16 by OlivierLagneau
|
|
Hi Tom, Here we are trying to answer your questions and remarks. Some of them need further investigation however. We certainely could help further if we could have a hand on your NetBeans/Eclipse project. Thanks again for this great feedback. - import netbeans project does not use the same build path (build/bin instead of build/compiled) That is expected, and we did this voluntarily. We have kept the NetBeans and Eclipse build system indepedents. So that your project will still be usable as a Netbeans project, even if you have moved to Eclipse plugin. - import netbeans project does not correctly handle \jfxtras-common\${platforms.default_fx_platform.lib}\jre\lib This comes from the way we are currently integrating with Eclipse build project features. Eclipse has both properties that are related to your project as in NetBeans, and some other properties related to the workspace. We need to improve the translation of properties from Netbeans to Eclipse, on the workspace properties area in this case. This is something that will be fixed in the next release. In the meantime, as a work-around you can fix that by manually updating the CLASSPATH to point to these libs. - you cannot specify which JavaFX to use (Exadel’s allow to specify the combination) Yes. This version does not provide that and is closely coupled with JavaFX 1.2.1. In the next release this will be different and you will be able to specify JavaFX SDK you want to run against. - you need to manually include deploy.jar and javaws.jar from the java (jdk/jre) lib in the project or in the used installed JRE We don't see how this can happen. We need to have a look on your NetBeans and Eclipse projects to investigate further. That may be a bug but we need to investigate. - Java classes are not correctly imported in JFX classes (XDialog uses DialogStage but there is an error: “cannot find symbol symbol : class DialogStage location: class org.jfxtras.stage.XDialog”) DialogStage is compiled. Again that should be working. We think this a similar issue as the above problem. We need to investigate further with your projet. - in the package explorer packages with just JFX classes are visually shown as empty (map icon is white, not orange) This is due to the current integration with Eclipse project builder. This is currently a limitation of Eclipse handling java alien dynamic languages. Integrated properly with JDT (Java Dynamic Toolkit for Eclipse) will fix this problem. The next release will be integrated with JDT and that should fix this problem. - after include deploy.jar and javaws.jar to the used Installed JRE, they are not present in the runtime path This is surprising . That may be a bug. You can however add in classpath rather than editing JRE settings to fix that. That also needs some investigation with your project at hands. - C:\Documents and Settings\User\My Documents\NetBeansProjects\jfxtras\common\src\org\jfxtras\app\XLauncherEnvironment.java:30: package com.sun.deploy does not exist. import com.sun.deploy.Environment; That seems similar to the previous question. It Needs investigation. Hope that helps. Olivier Lagneau, |
|
OlivierLagneau
|
Posted: January 23, 2010 18:03 by OlivierLagneau
|
|
Hi Tom, Thanks for the feedback and discussion on last Thursday. We will provide you very soon feedback on the problems you met. The Eplugin2 team |
Replies: 3 - Last Post: January 23, 2010 18:03
by: OlivierLagneau
by: OlivierLagneau
