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: | "Keep JavaFX RT artifacts on class path" option is both broken and dangerous | ||
---|---|---|---|
Product: | javafx | Reporter: | swpalmer <swpalmer> |
Component: | Project | Assignee: | Roman Svitanic <rsvitanic> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | P3 | ||
Version: | 8.0 | ||
Hardware: | Macintosh (x86) | ||
OS: | Mac OS X | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
swpalmer
2014-01-14 23:35:28 UTC
Perhaps I am misunderstanding the intent of this feature. Is it intended to only keep the javafx class on the COMPILE classpath for when you are using Java 7 ? Therefore allowing you to deal with getting it on the runtime class path in your own code. We do something like this with one of our products where we hack jfxrt.jar onto the classpath at runtime in a J2SE project because we are not using the JAvFX launcher (it's a Swing app with a JFXPanel). If so it doesn't belong in the Deployment section. Implemented in the JFX Project. (In reply to swpalmer from comment #1) > Is it intended to only keep the javafx class on the COMPILE classpath for > when you are using Java 7 ? Therefore allowing you to deal with getting it > on the runtime class path in your own code. You are right, option is labeled as "Keep JavaFX RT artifacts on Compile Classpath if not present by default". From this label it is obvious that this option affects only the compile classpath. Therefore I think on JDK7 it does what is expected. > If so it doesn't belong in the Deployment section. I agree, this may not be the most appropriate place to place this option, but this definitely won't be a P3 issue. |