-
Bug
-
Resolution: Incomplete
-
P4
-
None
-
8
-
SceneBuilder 2.0-b20
Windows 7 x64
SceneBuilder 1.0 recognized the <?scenebuilder-classpath-element?> tag, and would properly include external libraries and load the scene.
However, this no longer seems to work SceneBuilder 2.0 (at least for JARs and .class files that extend JavaFX components). I'm forced to open the GUI and import the libraries into SceneBuilder to get them into it's classpath to get things to work. I haven't been able to find any information about this tag being deprecated in the new version of SceneBuilder or not.
Furthermore, even when I've imported the libraries into SceneBuilder, if I double-click on an FXML file to launch SceneBuilder using the default file application associated with it, I get missing class errors. I have to launch SceneBuilder and then File > Open in order for it to work properly. I looked at the SceneBuilder logs, and I see the "INFO: Start exploring JAR my/path/to.jar" messages, so there's something weird going on.
However, this no longer seems to work SceneBuilder 2.0 (at least for JARs and .class files that extend JavaFX components). I'm forced to open the GUI and import the libraries into SceneBuilder to get them into it's classpath to get things to work. I haven't been able to find any information about this tag being deprecated in the new version of SceneBuilder or not.
Furthermore, even when I've imported the libraries into SceneBuilder, if I double-click on an FXML file to launch SceneBuilder using the default file application associated with it, I get missing class errors. I have to launch SceneBuilder and then File > Open in order for it to work properly. I looked at the SceneBuilder logs, and I see the "INFO: Start exploring JAR my/path/to.jar" messages, so there's something weird going on.