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.
Created attachment 141852 [details]
libs.javafx module and changes in module system
Created attachment 142288 [details]
New patch together with changes to core.browser.webview module
I'd like to integrate on Monday, tomorrow.
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?
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.