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.

Bug 237973 - org.netbeans.libs.javafx to hide differences between JDK7 and JDK8
Summary: org.netbeans.libs.javafx to hide differences between JDK7 and JDK8
Status: RESOLVED FIXED
Alias: None
Product: platform
Classification: Unclassified
Component: Module System (show other bugs)
Version: 8.0
Hardware: PC Linux
: P1 normal (vote)
Assignee: Jaroslav Tulach
URL:
Keywords: API_REVIEW_FAST
Depends on:
Blocks: 242564 238509 238939
  Show dependency tree
 
Reported: 2013-11-05 07:39 UTC by Jaroslav Tulach
Modified: 2014-03-06 09:42 UTC (History)
2 users (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

Attachments
libs.javafx module and changes in module system (13.72 KB, patch)
2013-11-05 07:42 UTC, Jaroslav Tulach 		Details | Diff
New patch together with changes to core.browser.webview module (21.16 KB, patch)
2013-11-17 21:31 UTC, Jaroslav Tulach 		Details | Diff
Show Obsolete (1) Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jaroslav Tulach 2013-11-05 07:39:51 UTC 
Now, when NetBeans runs only on JDK7, we may use JavaFX features more extensively. Alas, the packaging of JavaFX is different on JDK7 and JDK8. To hide these differences, I propose we create a special module that hides them.

Users of JavaFX will depend on this module and the module system makes sure they will have necessary javafx.* classes on classpath.
Comment 1 Jaroslav Tulach 2013-11-05 07:42:20 UTC 
Created attachment 141852 [details]
libs.javafx module and changes in module system
Comment 2 Jaroslav Tulach 2013-11-17 21:31:22 UTC 
Created attachment 142288 [details]
New patch together with changes to core.browser.webview module

I'd like to integrate on Monday, tomorrow.
Comment 3 Jaroslav Tulach 2013-11-18 08:51:14 UTC 
core-main#61d89372c0b8
Comment 4 Milos Kleint 2013-12-05 16:21:31 UTC 
this caused https://jira.codehaus.org/browse/MNBMODULE-228

never before we had expressions in Class-Path: manifest entries. Is it even valid from standard java point of view?
Comment 5 Jaroslav Tulach 2013-12-05 22:16:00 UTC 
No it is not valid from Java point. But our interpretation of Class-Path tag was always more relaxed - for example we support ".." as a reference to parent, while Java does not.

Another related problem is bug 238939.