|
|
|
|
|
|
Re: JavaFX 8u20 support in e(fx)clipse [message #1443772 is a reply to message #1443737] |
Mon, 13 October 2014 07:35 |
Christoph Keimel Messages: 482 Registered: December 2010 Location: Germany |
Senior Member |
|
|
Did you add "org.eclipse.fx.javafx"
as a dependency to "org.controlsfx" in its MANIFEST.MF?
This is what our MANIFEST.MF for ControlsFX looks like:
Manifest-Version: 1.0
Bundle-ManifestVersion: 2
Bundle-Name: Controls FX
Bundle-SymbolicName: de.emsw.gosa.lib.controlsfx;singleton:=true
Bundle-Version: 8.0.7
Bundle-ClassPath: .,
controlsfx-8.20.7.jar,
openjfx-dialogs-1.0.2.jar
Export-Package: javafx.scene.control,
org.controlsfx,
org.controlsfx.control,
org.controlsfx.control.action,
org.controlsfx.control.cell,
org.controlsfx.control.decoration,
org.controlsfx.control.spreadsheet,
org.controlsfx.control.table,
org.controlsfx.control.table.model,
org.controlsfx.control.textfield,
org.controlsfx.dialog,
org.controlsfx.glyphfont,
org.controlsfx.property,
org.controlsfx.property.editor,
org.controlsfx.tools,
org.controlsfx.validation,
org.controlsfx.validation.decoration
Bundle-RequiredExecutionEnvironment: JavaSE-1.8
Require-Bundle: org.eclipse.fx.javafx;bundle-version="2.2.0";visibility:=reexport
Bundle-ActivationPolicy: lazy
|
|
|
Re: JavaFX 8u20 support in e(fx)clipse [message #1443782 is a reply to message #1443772] |
Mon, 13 October 2014 07:46 |
Thomas Schindl Messages: 6651 Registered: July 2009 |
Senior Member |
|
|
I suggest to use package imports instead of require-bundle but it is
important that you all packages referenced are imported else OSGi does
not know from where it should load the references.
I'm more and more leaning towards NOT using "org.eclipse.fx.javafx" and
the OSGi Hooks in a e4+JavaFX application but starting Equinox with
-Dorg.osgi.framework.bundle.parent=ext.
This makes:
a) all package imports needless
b) other stuff like Nashorn work appropriately
The only thing left which requires "org.eclipse.fx.javafx" is when you
try to integrate into the Eclipse IDE or any other Equinox-Application
which requires to launch with the obscure default classloading strategy.
Thoughts?
Tom
On 13.10.14 09:36, Christoph Keimel wrote:
> Did you add "org.eclipse.fx.javafx"
> as a dependency to "org.controlsfx" in its MANIFEST.MF?
>
> This is what our MANIFEST.MF for ControlsFX looks like:
> Manifest-Version: 1.0
> Bundle-ManifestVersion: 2
> Bundle-Name: Controls FX
> Bundle-SymbolicName: de.emsw.gosa.lib.controlsfx;singleton:=true
> Bundle-Version: 8.0.7
> Bundle-ClassPath: .,
> controlsfx-8.20.7.jar,
> openjfx-dialogs-1.0.2.jar
> Export-Package: javafx.scene.control,
> org.controlsfx,
> org.controlsfx.control,
> org.controlsfx.control.action,
> org.controlsfx.control.cell,
> org.controlsfx.control.decoration,
> org.controlsfx.control.spreadsheet,
> org.controlsfx.control.table,
> org.controlsfx.control.table.model,
> org.controlsfx.control.textfield,
> org.controlsfx.dialog,
> org.controlsfx.glyphfont,
> org.controlsfx.property,
> org.controlsfx.property.editor,
> org.controlsfx.tools,
> org.controlsfx.validation,
> org.controlsfx.validation.decoration
> Bundle-RequiredExecutionEnvironment: JavaSE-1.8
> Require-Bundle:
> org.eclipse.fx.javafx;bundle-version="2.2.0";visibility:=reexport
> Bundle-ActivationPolicy: lazy
>
|
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.05660 seconds