Hi all, As a follow-up to the recent discussion on separating the applications from the framework, I’d like to propose creating a new Git repository named *ofbiz-applications*.
Discussion thread: https://lists.apache.org/thread/8rvtlfyo3hqg1kgmmo9t9tybw5vjfqt9 Over the past several weeks, we’ve completed the dependency cleanup work tracked under *OFBIZ-13305*. The framework no longer has runtime dependencies on the applications, and the remaining references have either been removed or migrated into the framework where appropriate. The goals of creating a separate repository are to: - Decouple the applications from the framework. - Allow the framework and applications to evolve independently. - Simplify the framework repository and make it easier to use as a standalone foundation. - Make framework upgrades significantly easier for adopters. Today, one of the biggest challenges when upgrading OFBiz is merging changes in the application layer, where business logic often conflicts with custom implementations. As a result, many adopters postpone framework upgrades, making it more difficult to benefit from the latest framework improvements, bug fixes, performance enhancements, and, most importantly, security fixes. By separating the applications from the framework, adopters will be able to upgrade the framework independently while keeping their customized application code unchanged. This will significantly reduce merge conflicts, simplify framework upgrades, and encourage users to stay current with the latest framework releases, including *critical security* updates. If any additional dependencies are discovered after the split, we can address them through follow-up JIRA issues without blocking the repository separation. Unless there are any objections, I’d like to proceed with creating the new *ofbiz-applications* Git repository and then begin migrating the application modules from the ofbiz-framework repository. Please share your feedback or concerns. Thanks -- Deepak Dixit ofbiz.apache.org
