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
Hey a new year has begun, let’s have a look of past year to see JRebirth highlights.
We have delivered more than 20 releases since the beginning, near to 5 official release per year during 4 years.
If we are looking overall download count from Maven Central in 2015, we can observe an amazing download peak in August, Summer is a great season to play with JRebirth 😀
On Friday the 23th of October I have talked about JRebirth Application Framework during Soft-Shake 2015 conference (Geneva, Hepia).
This was the first time I talked only about JRebirth, pretty hard task to explain the JRebirth abstraction and its benefits.
Once again I shipped all family with me to discover Switzerland !! We have visited an interesting museum, the cathedral and the United Nations palais.
I have recently migrated to Eclipse Mars, and it provides an interesting tool that tracks all UI freezes.
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).