I’m pleased to inform you that we have finally released JRebirth 8.0.2.
This is the third release of the 8.x branch that will be merged on the master branch soon.
You can find the full release notes here : sites.jrebirth.org/org.jrebirth-8.0.2/releaseNotes.html
and the installation procedure here: sites.jrebirth.org/org.jrebirth-8.0.2/doc/Installation.html
and hopefully the last…
People that follow the mailing list are already aware of that, but some guys had made unnecessarily offensive and insulting remarks on the mailing list (but also on JRebirth’s email). I just want to repeat that this is an open source project that is free, I reply to question asked politely as fast as I can (most often in few hours, even minutes). So if you need more be patient, contribute or donate !
Unhappily I couldn’t help these guys because they don’t clearly ask something.
However I have noticed that the 8.x release can be broken for some people depending on which repositories they used, and when they had updated them.
I have performed a refactoring of the Bintray structure, and the Organization pom (parent pom of org.jrebirth.af) has not been synchronized with Maven Central nor with JCenter (but was available into OJO and our local artifactory instance). Therefore the usage of org.jrebirth.af:core artifact could be broken. This problem is lost to history for 8.0.1 and 8.0.2 version since all artifacts have been synced on all repositories.
I want to send my special thanks to Bintray‘s support team that helps me to fix JRebirth Bintray configuration in order to release all JRebirth artifacts correctly. Now each main Github’s repository of JRebirth Organization has its own Bintray’s package (synced to JCenter and Maven Central).
Definitely “Froggies” really rock binaries management !
This new version adds a small enhancement to finfd javafx nodes held into an FXMLComponent. it also improves distribution of showcases modules by enabling gain the pack200 option and repair version used for Sample maven archetype.
The latter point is a regression implied by the usage of mvn-release plugin that doesn’t update version used into archetype’s pom.xml. I switch back to manual versioning. I have spent some time trying to update the build process to do like Axel Fontaine describes on his blog but there are some leaks for archetype, website/documentation. Another thing to try will be to use the push to bintray feature of newer artifactory application to replace current maven profiles used.
8.0.2 version is available on:
- Maven Central ( http://search.maven.org )
- OJO (http://oss.jfrog.org)
- Bintray repository (https://bintray.com/jrebirth/JRebirth/JRebirthAF/8.0.2/view#files)
- and also JCenter repository (http://jcenter.bintray.com/org/jrebirth/af/core/8.0.2/)
- JRebirth repository (http://repo.jrebirth.org)
8.0.2 – Maintenance Release 2015-06-23
This release add two minor improvements and fixes sample archetype.
- Fix archetype generation #152
Fix version used by sample module, it was using old snapshot version.
- Active pack200 for showcases #151
Re-active pack200 for showcases modules, it was broken since Java8 migration.
- Add lookup method into FXMLComponent #149
Add convenient methods used to search a given node loaded from a fxml file.