The Broadleaf framework 4.0.0 release candidate is now available.
Broadleaf 3.1.13-GA and 3.0.16-GA are released on Maven Central. This contains a patch to a security vulnerability in the Broadleaf admin panel that allowed an admin user to hijack another admin user's account. Customer-facing logins were unaffected. We recommend immediate upgrades to these latest versions of Broadleaf in order to patch this security vulnerability. See the details for full release notes.
New Broadleaf CE releases for 3.1.10-GA and 3.0.15-GA have been published to Maven Central. Release notes for those respective releases:
These releases were in response to critical bugs present in 3.1.9-GA and 3.0.14-GA. We recommend skipping those releases and upgrading straight to 3.1.10-GA or 3.0.15-GA.
New Broadleaf CE releases for 3.1.9-GA and 3.0.14-GA have been published to Maven Central. Release notes for those respective releases:
Edit on December 3, 2014: These releases contain a critical bug. We recommend skipping these releases and go straight to 3.1.10-GA or 3.0.15-GA instead. Those 2 releases contain all of the fixes in 3.1.9-GA and 3.0.14-GA, along with the critical bug fix.
This chronicles my experience as both an attendee and a speaker at SpringOne 2GX 2014 in Dallas, Texas.
The latest patch releases in the 3.0 and 3.1 lines have been released!
In part 2 of my dive into Groovy and Gradle, this post talks about the actual implementation of a Rackspace Cloud Files file provider using the Groovy language.
This is the 2nd patch release in the 3.1 line of the Broadleaf Commerce community edition and includes 31 closed issues on GitHub.
This is the first post in a 2-part series detailing my experience with writing a Broadleaf file provider module for Rackspace Cloud Files. Rather than using Maven and vanilla Java, I wrote the module using Gradle to build the Groovy implementation code. This first part details the Gradle configuration required with some details about how that compares to using a Maven pom.xml.
We have begun using New Relic for our application monitoring at Broadleaf. We noticed a very disturbing trend with increasingly high 'Request Queueing' time. This chronicles our journey into how we resolved it.
Broadleaf has officially switched off of Jira and has moved all issue tracking to GitHub across all projects. This details how Broadleaf uses GitHub to manage bug tracking, pull requests and releases.
While you might think that the @OrderBy and @OrderColumn JPA annotations are the same, there is actually a very subtle difference that can cause null values to appear in an @OneToMany list.