| Major changes in 2.0.0 nightly builds [message #1688516] |
Fri, 20 March 2015 18:32  |
Eclipse User |
|
|
|
Hi,
If you have a e4 + JavaFX applications and are running with the target
platform set to the nightly repo you'll have to make some adjustments to
your launch configs.
a) org.eclipse.fx.osgi & org.eclipse.fx.javafx are not part of the
default target feature if you want them you need to add
org.eclipse.fx.runtime.min.feature in your target platform
b) We advice you to *not* use the bundles from a) but change your
project like this:
- remove ALL javafx.*, com.sun.javafx, ... imports (you should see
errors for packages who can not be imported)
- update your launchconfigs & .product
- remove -Dosgi.framework.extensions=org.eclipse.fx.osgi
- add -Dorg.osgi.framework.bundle.parent=ext
c) javax.annotation is not shipped anymore with the target-platform but
we ship javax.annotation.jre which effectively is empty and only
there to allow interopt with the e4 core platform who does
javax.annotation imports, we are working with e4 to make those
import package directives at least being marked optional
=> adjust your features to use javax.annotation.jre
=> adjust launch configs who are based on plugins to use
javax.annotation.jre
d) we suggest that you check ALL your MANIFEST.MF and
a) remove javax.annotation imports
b) if a) is not possible you make the import *optional*
We fully understand that those are somehow disruptive changes but in the
long run we are sure they help the adoption of e4 on JavaFX.
Tom
|
|
|
|
|
|
| Re: Major changes in 2.0.0 nightly builds [message #1690684 is a reply to message #1688516] |
Mon, 30 March 2015 11:27  |
| Eclipse User |
|
|
|
Hi,
Minor update for those useing the javafx-packager you should update your
build.xml to include and make it look like this:
> <fx:platform basedir="${java.home}">
> <fx:property name="org.osgi.framework.bundle.parent" value="ext"/>
> </fx:platform>
Tom
On 20.03.15 23:32, Tom Schindl wrote:
> Hi,
>
> If you have a e4 + JavaFX applications and are running with the target
> platform set to the nightly repo you'll have to make some adjustments to
> your launch configs.
>
> a) org.eclipse.fx.osgi & org.eclipse.fx.javafx are not part of the
> default target feature if you want them you need to add
> org.eclipse.fx.runtime.min.feature in your target platform
>
> b) We advice you to *not* use the bundles from a) but change your
> project like this:
> - remove ALL javafx.*, com.sun.javafx, ... imports (you should see
> errors for packages who can not be imported)
> - update your launchconfigs & .product
> - remove -Dosgi.framework.extensions=org.eclipse.fx.osgi
> - add -Dorg.osgi.framework.bundle.parent=ext
>
> c) javax.annotation is not shipped anymore with the target-platform but
> we ship javax.annotation.jre which effectively is empty and only
> there to allow interopt with the e4 core platform who does
> javax.annotation imports, we are working with e4 to make those
> import package directives at least being marked optional
> => adjust your features to use javax.annotation.jre
> => adjust launch configs who are based on plugins to use
> javax.annotation.jre
>
> d) we suggest that you check ALL your MANIFEST.MF and
> a) remove javax.annotation imports
> b) if a) is not possible you make the import *optional*
>
> We fully understand that those are somehow disruptive changes but in the
> long run we are sure they help the adoption of e4 on JavaFX.
>
> Tom
>
|
|
|
Powered by
FUDForum. Page generated in 0.06039 seconds
Home