Improved: Use ‘depends-on’ attribute instead of “component-load.xml” (OFBIZ-11296) We currently have two ways to define component loading order. Either by using ‘depends-on’ attribute in “component-config.xml” or by adding a “component-load.xml” file at the root of a component directory.
“depends-on” is more flexible because it handles partial ordering when “component-load.xml” defines a total order which is not necessarily meaningful, so it is better to rely only “depends-on”.
This removes the usage of “component-load.xml” to use ‘depends-on’ instead. The dependency declarations correspond to the total ordering previously defined but will need to be refined in the future to relax unnecessary dependency declarations.
Only “framework/base/config/component-load.xml” which defines the top-level directories order (framework, applications, themes and plugins) is kept.
Improved: PicklistStatusHistory doesn't follow history entity status pattern (OFBIZ-11182) The entity PicklistStatusHistory record each status change realized on picklist. It can't be convert to entity-auto easily because PicklistStatusHistory's fields pattern doesn't follow same entities like ShipmentStatus and PartyStatus.
To solve this issue, I deprecate PicklistStatusHistory and move it to OldPicklistStatusHistory and replace it by new entity PicklistStatus that can use natively with entityauto.
I added a new migration service migrateOldPicklistStatusHistoryToPickListStatus to forward all picklist status history to new entity.