- v1.0.0-latest-prod
Fix ORA-00920: invalid relational operator exceptions during workflow transitions in the admin for installations using Oracle.
In a manifest-based installation, fix parent references in a generated liquibase changelog for a component customization.
Workflow transition performance refactoring. See Workflow Transition Performance.
As of Broadleaf Release Train 2.0.0-GA, all common libraries have been upgraded to Spring Boot 3.
This version includes all changes up to 1.5.14-GA
Updated compatibility measures to log a warning message when ignoring attempts to change the column type that are not backward compatible
During legacy initialization (during app boot), preserve schema case for Postgres Liquibase schemas to address Liquibase bug causing SQL syntax errors for schema names containing a hyphen
Allow for zero-arg instantiation of StringSetType objects
Added a new character long object (CLOB) length constant in JPA constants
Fix ORA-00920: invalid relational operator exceptions during workflow transitions in the admin for installations using Oracle.
Stopped separating destructive change sets by default when running UtilitiesIT
Separating destructive change sets is useful for Broadleaf developers to ensure backwards compatibility when modifying data schema.
Users of Broadleaf do not need to have the same restriction in place since they are not developing the framework but using it.
"Destructive change sets" include modifying the data type of an existing column.
Updated OracleBaseProvider’s wait strategy to use the same 900 second timeout value instead of using the 240 second default
Fixed issue with resolving filesystem paths on Linux that contain spaces
Added ability to remove drop changelogs from the newly copied changelog file during initial construction
The property schema.utils.remove.drop.includes can be assigned the values true or false in order to toggle the removal of drop changelogs
Added ability to define delegate data source url using placeholder properties.
Specifically, the property broadleaf.composite.datasource.url can be assigned the value 'jdbc:postgresql://${mytest.hostname}:${mytest.port}/broadleaf' and those placeholders will be resolved if defined.