This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | JavaFX Application Project fails to run or debug when dependent on another javafx project | ||
---|---|---|---|
Product: | javafx | Reporter: | sldr <sldr> |
Component: | Project | Assignee: | Petr Somol <psomol> |
Status: | RESOLVED INCOMPLETE | ||
Severity: | normal | CC: | sldr |
Priority: | P3 | ||
Version: | 7.1.2 | ||
Hardware: | PC | ||
OS: | Windows 7 | ||
Issue Type: | DEFECT | Exception Reporter: | |
Bug Depends on: | 213219 | ||
Bug Blocks: |
Description
sldr
2012-05-30 00:15:19 UTC
Thanks for finding this out. Actually I see the problem relates to the build/deployment process that takes place in FX Applications; the existence of Application class is assumed when calling FX SDK deployment tasks. It seems we will need a JavaFX Class Library project type as counterpart of Java Class Library to make things straightforward. I created a separate issue for that: issue 213219. As for "Duplicated project name in import" - this is not the reason of the problem. See issue 208484. It works for me in the latest Dev build. In project.properties, there is a different order of targets in run.classpath, comparing to 7.2 Beta and earlier... (In reply to comment #2) > It works for me in the latest Dev build. In project.properties, there is a > different order of targets in run.classpath, comparing to 7.2 Beta and > earlier... I have tried to create a FX Application with unchecked "create application class" in the creation wizard to serve as library, then made a dependence on it from another FX Application and I can confirm this works in the current daily build. This is due to recent fixes of other indirectly related issues after 7.2beta. Thus I am closing this particular issue, but I am leaving the JavaFX Class Library task (issue 213219) open because proper JavaFX library support would be better for at least the following reasons: a FX Application serving as a library fails ungracefully when attempted to run directly, during build process it creates invalid deployment artifacts as if it was a launchable application although this is not the case, dedicated JavaFX Class Library type would be more intuitive as of its purpose. Thanks for quick response. I am looking forward to 7.2... |