2.0.0
There are two main themes for the 2.0 release: free the runtime from unecessary/artificial stumbling blocks; and revise APIs to better align with Java 8 and fix API glitches
1. Free the runtime from unecessary stumbling blocks
One of the major problem is how the integration of JavaFX is done into OSGi with the help of adapter hooks because the SWT-Integration layer has no other choice than to construct custom classloaders. We plan to free pure e4+JavaFX applications from the AdapterHook burden and simply make Equinox classloader delegation do its job. Other problems we are going to target is the somehow strange interaction with javax.annotation.PostConstruct and javax.annotation.PreDestroy who cause constant pain to adopters.
2. Revise APIs to better align with Java8 and fix API glitches
We have some APIs who e.g. support updateing your application who are not very Java8 friendly and others who didn't do their job. A list of break API breaks can be retrieved with this query.
The project leadership certifies that the APIs in this release are "Eclipse Quality".
There have been no security vulnerabilities
User documentation eg useage recipes are provided at https://wiki.eclipse.org/Efxclipse/Runtime/Recipes and has been extended showing new features in use (eg the new memento API at https://wiki.eclipse.org/Efxclipse/Runtime/Recipes#UI-State_Persistence_with_Memento-Interface)
We are also very proud that people from the community started writing tutorials on how to work with e(fx)clipse runtime components:
- Dirk Fauth (https://www.codecentric.de/) has written a blog about the migration from e4-SWT-RCP to e4-JavaFX-RCP (https://blog.codecentric.de/en/2015/02/swt-javafx-migration-eclipse-rcp-cookbook/)
- Christoph Keimel (http://www.kware.net) has written a blog about the migration from e4-SWT-RCP to e4-JavaFX-RCP with the help of SWT on JavaFX (http://www.kware.net/?p=64)
We managed to grow the community
- we see a steady flow of question at our newsgroup (multiple requests per week) and we are proud that we can once more end the release cycle with having answered all of the questions!
- we see adoption of e4+JavaFX in the industry and BestSolution.at helps various customers around to world to develop the next generation RCP application on top of e4+JavaFX
- we once more got multiple contributions from externals. Most of them added new functionality in the runtime components