Since JRebirth 8.5.0 version, all demo applications have been reviewed and their web pages have been homogenized.
Now you can download each application in three different formats:
- A self-executable jar ( java- jar myApp.jar)
- A Windows executable
- A zipped archive containing a jnlp file with libraries (javaws -offline -Xnosplash myApp.jnlp
This post will describe briefly how we are managing the release of all JRebirth artifacts by using Maven Build, Jenkins, Artifactory, Bintray/JCenter and Nexus.
All JRebirth artifacts are deployed to several repositories as explained into the official documentation page : Installation
As you probably know, JRebirth is built using Maven tool, really convenient to package binaries, javadoc and sources jar but also to make and deploy the jrebirth website with syntax highlighting (thx to doxia include macro). It allows to break the build if a piece of code used into documentation is missing (ie: after some refactoring changes).
A lot of blog posts are related to CDI for JavaFX applications.
But why do you need to add a complex mechanism to perform simple task, you will answer that all these magical things will simplify developer’s life.
You ‘re wrong, magic things that add additional stuff are not so useful
Why should we inject loader or other utilities classes to do a common task ?
Last year I decided to create an application framework dedicated to JavaFX; the brand new graphical toolkit for Java.
After having played with Swing, SWT/JFaces, Flex, Silverlight and for sure Web API during several years I wanted to go back to Swing…
… and JavaFX 2 had been launched.
I hate Ant, and I can’t begin to work on a project that requires using it.
So like many people I want to build my brand new JavaFX 2 applications with the best toolchain available for Java : Maven.
I planned to create a custom maven-plugin to do the job, but by using existing ones we can do it.
Some things must be improved but the essential works.
The results is a zip file containing all dependencies (jar) with a jnlp file used to launch the application online or offline.