!!WARNING!!: This release contains 2 critical issues: 619 and 620. We recommend skipping this release and instead going straight to 3.0.8-GA.
Broadleaf 3.0.7-GA Release
Released on December 31, 2013
Broadleaf 3.0.7-GA is now available on Maven central. As this is a patch release to the 3.0 line, we recommend upgrading immediately, no migration necessary. Read on for additional release information.
This is the 7th patch release in the Broadleaf 3.0 line. Quite a few major bugs were resolved in this release, mainly related to various problems in the admin. A few were specifically related to modifying and creating existing admin users. One of the most notable resolved issues is a bug that has existed in Broadleaf for years where an error message was logged on startup (#58). While it did not actually cause a real issue (like broken functionality) it was a red herring for other underlying problems. We also sped up the build time of the framework by over 1 minute by updating the maven source plugin that we were using (see #583).
An at-a-glance view of the issues that were closed in this release:
Critical Bugs(1)
Major Bugs(10)
- Admin Salt encryption Issue
- Rule builders do not allow fields with method names
- Hibernate logs a 'hibernate.connection.autocommit false break the ejb3 specification' warning on startup
- No enumeration values are displayed when the number of values equals 5
- product translation do not work in admin module for Demosite
- FulfillmentGroupItemStrategyImpl verify method quanity comparison error
- The admin does not internally utilize the currency resolver to resolve default currency
- Offers with multiple targets do not apply discounts correctly
- Move mergeCart processing into CartStateFilter
- IsPresent rule builder operator does not work for custom field
Minor Bugs(4)
- Unable to run legacy tests
- AddressService and StaticAssetService methods not wrapped in transations
- If an admin user is created by another admin user without associating the default role, cookie clearing is required
- Null PersistenceUnitRootUrl during Ejb configuration error
Enhancements(10)
- Update translatable items when a locale switch occurs
- Admin should validate that full URL fields start with a leading slash and do not end with one
- Update the maven-source-plugin to remove 'Source already added' log messages when building the framework
- Root pom.xml points to the wrong URL for nexus deployment
- Startup excessive logging and start up time
- ExtensionManager contract is confusing
- When OfferItemCriteriaRuleType is null, it should default to NONE
- OfferAuditDao uses query.Catalog cache that may not work properly in load balanced environments
- Spring Security filters are being invoked for calls for BLC managed assets
- Admin user management validation errors in 3.0.X
Total Resolved Issues: 25