|
Sort Order:
[
Permalink
| « Hide
]
Bratukhin, Andrey added a comment - 13/Apr/10 01:50 AM
Please, fix it asap.
Integrated in exadel-javafx-plugin-continuous #42 (See [http://hudson.exadel.org/hudson/job/exadel-javafx-plugin-continuous/42/])
FXP-43 I've just updated to the 1.3.0.N14 version of the plugin and this issue doesn't seem to be fixed. I'm still getting the same compilation errors as before.
Integrated in exadel-javafx-plugin-continuous #62 (See [http://hudson.exadel.org/hudson/job/exadel-javafx-plugin-continuous/62/])
FXP-43 - Resolving of variable classpath entry are fixed Compilation and building are fixed
I have installed version 1.3.1 N15 of the plugin and this issue is still occurring.
My environment: JDK 1.6.0_16 Eclipse 3.5 SR2 JavaFX SDK 1.3 Ubuntu Linux 8.04 I have a multi-module project where each module is an Eclipse project. One of the projects contains all the third-party jars. Other projects reference the jars in this lib project.
I've attached a couple of jars with two Eclipse projects in them. Integrated in exadel-javafx-plugin-continuous #67 (See [http://hudson.exadel.org/hudson/job/exadel-javafx-plugin-continuous/67/])
FXP-43 - JavaFX Nature detecting was fixed Kevin, I think, you have missed some configuration for your projects. I have successfully created multi-module project from your jars. See my attached screenshots.
As I understand from you example, you have created projects by maven. But our plug-in works only with projects, that have Java Nature or Exadel JavaFX Nature. You should add Java/JavaFX Nature to all necessary projects. My environment: JDK 1.6.0_20 Eclipse 3.5 SR2 JavaFX SDK 1.3 Kubuntu 10.04 LTS Hi Andrey,
I've added the Java builder and nature to the exadel-fxp43-lib project and added the jars to the build path of that project but the exadel-fxp43 project still can't see classes from the JFxtras jar. I'm not using Maven, I just use the same directory structure. In any case it shouldn't make any difference. Why does the lib project require a JavaFX nature? Its just a container for jar files. There is nothing to be built in that project. Its only the project containing source code that needs to be built and it references the jars in the lib project. Are you able to package up the sample project that you managed to get working and attach them to this jira? I'll see if they work for me. See worked multi-module project.
exadel-fx43-lib in my case doesn't have JavaFX nature, but only Java nature. Java Nature is necessary for our implementation, because it provides API to analyze dependencies and Java types.
Ok, I've got it working now. Thanks for the sample project.
To summarise, as you suggested, the fix was to add the Java nature to the lib project but then the JavaFX project must also reference the lib project as a project reference in its build path. Just referencing the jars directly was not enough. This is inconsistent with the way the Java builder works. There is no need to define a lib project with a Java nature and there is no need to add the lib project as a project reference. I'm wondering if it is really necessary for the JavaFX plugin to be implemented in this way. Maybe this should be raised as a separate issue. Anyway, thanks for your help in getting it working for me. |
|||||||||||||||||||||||||||||||||||||||||||||||||
Bug
Closed
Major
Referencing other projects and Jars on Java Build Path is not working
