Is Exadel currently compatible with Eclipse Helios? I just installed the (latest) Exadel plugin following instructions from http://download.exadel.org/javafx_plugin/docs/guide/#installation, and I'm having some issues.
Isn't the plug-in supposed to detect what needs to be imported when specific components are used? I'm testing things out with a simple Button node, and there is no suggestion regarding how to fix the problem. When I try to "Organize Imports", it detects the proper import path (javafx.scene.control.Button), but when I try to import, I get the following error message:
Unexpected error in organize imports. See log for details.
org/eclipse/jdt/internal/core/SourceRange"
I'd really like to get this working, as it's a hassle trying to coordinate a project between Eclipse and NetBeans (which is the only viable option for JavaFX right now). Any help would be great!
Helios is not yet supported,
Helios is not yet supported, it's work in progress: http://jira.exadel.org/browse/FXP-71
Please bring helios support
Just giving some encouragement for getting a working version on helios.
Many thanks!
Patch for helios support
Actually getting it to compile for Helios is a simple thing, here's the patch for current svn version:
Index: src/com/exadel/javafx/ide/internal/ui/scripteditor/actions/refactoring/ImportRewrite.java
===================================================================
--- src/com/exadel/javafx/ide/internal/ui/scripteditor/actions/refactoring/ImportRewrite.java (revision 156)
+++ src/com/exadel/javafx/ide/internal/ui/scripteditor/actions/refactoring/ImportRewrite.java (working copy)
@@ -13,7 +13,7 @@
import org.eclipse.jdt.core.ISourceRange;
import org.eclipse.jdt.core.dom.ASTParser;
import org.eclipse.jdt.core.dom.CompilationUnit;
-import org.eclipse.jdt.internal.core.SourceRange;
+import org.eclipse.jdt.core.SourceRange;
import org.eclipse.jdt.internal.core.util.Messages;
import org.eclipse.jface.text.BadLocationException;
import org.eclipse.jface.text.IDocument;
It seems to work fine, but I have not fully tested this.
So what's really holding you to get a 3.6 version out?
Thanks for help. I will
Thanks for help. I will integrate your patch to our branch for Helios. But we had many runtime issues.
beware not to break 3.5 support
With such change I don't think it will work in 3.5 and 3.6. Either you create a new branch (more of a hassle) or you find an equivalent class that works in both versions.
I don't have a 3.5 install at hand but I think using
org.eclipse.jdt.internal.corext.SourceRangeshould work on 3.6 and previous versions as well. It's just an additional warning in 3.6.So here's the new patch, working fine with 3.6 here:
Index: src/com/exadel/javafx/ide/internal/ui/scripteditor/actions/refactoring/ImportRewrite.java
===================================================================
--- src/com/exadel/javafx/ide/internal/ui/scripteditor/actions/refactoring/ImportRewrite.java (revision 156)
+++ src/com/exadel/javafx/ide/internal/ui/scripteditor/actions/refactoring/ImportRewrite.java (working copy)
@@ -13,7 +13,7 @@
import org.eclipse.jdt.core.ISourceRange;
import org.eclipse.jdt.core.dom.ASTParser;
import org.eclipse.jdt.core.dom.CompilationUnit;
-import org.eclipse.jdt.internal.core.SourceRange;
+import org.eclipse.jdt.internal.corext.SourceRange;
import org.eclipse.jdt.internal.core.util.Messages;
import org.eclipse.jface.text.BadLocationException;
import org.eclipse.jface.text.IDocument;