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

Summary:	org.netbeans.libs.javafx to hide differences between JDK7 and JDK8
Product:	platform	Reporter:	Jaroslav Tulach <jtulach>
Component:	Module System	Assignee:	Jaroslav Tulach <jtulach>
Status:	RESOLVED FIXED
Severity:	normal	CC:	apireviews, skygo
Priority:	P1	Keywords:	API_REVIEW_FAST
Version:	8.0
Hardware:	PC
OS:	Linux
Issue Type:	ENHANCEMENT	Exception Reporter:
Bug Depends on:
Bug Blocks:	242564, 238509, 238939
Attachments:	libs.javafx module and changes in module system New patch together with changes to core.browser.webview module

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.