Mathieu Lirzin <[email protected]> writes: > Here is a *big* change that I am considering for OFBiz to fixes those > issues by leveraging the Java platform which already provides everything > that we need to fix those issues: > > - Distributing OFBiz in a Jar with its XML files inside to fix #1 would > allow developpers to extend the framework without compiling it which > removes the hard dependency on Gradle which fixes #2 and #3 and make > the build process snappier. > > - the classpath can be used to compose an arbitrary list of plugins > from various location which fixes #4. > > - The ServiceLoader class [1] is a standard and stable extensibility > mechanism based on JAR metadata which can be used to scan the > available OFBiz components available across multiple JARs that can > replace Gradle complex component bundling to fix #5. > > The biggest challenge with this solution is that we need to do a huge > work of adapting OFBiz to to use location independant resources [3] when > loading XML and GroovyScript files.
I have opened OFBIZ-11161 [1] to implement that change. [1] https://issues.apache.org/jira/browse/OFBIZ-11161 -- Mathieu Lirzin GPG: F2A3 8D7E EB2B 6640 5761 070D 0ADE E100 9460 4D37
