+1 for lack of benefit (and for fear ;-))
My first thoughts: => If a change is desired, than Gradle would surely be a good choice as it is the next generation build tool witch tries to combine the advantages from tools like ant, maven and others… => I think the stability of Gradle is not a question as it is used by projects like Spring, Hibernate, Grails, Groovy and others… => With the ability to use ant tasks and whole ant build scripts within Gradle, a smooth migration could be an option => Maven rely on it’s convention over configuration pattern, so it is never a good idea to NOT follow it’s conventions by configuring it for a different project structure for example. So there may be the need for massive changes to the OFBiz project structure and so on. => Also the ability to only produce one artifact per project in maven would perhaps end up in configuring sub projects for each application and module in OFBiz with a frustrating handling of multi module configurations with version-/release-tags, dependency handling and so on... => I used maven in multi module project setups before and it has it’s nice features, although it is sometimes hard to understand details and effects of the build lifecycle or single plugins. But the main fact is, that this were green-field projects, so things in terms of convention over configuration are much easier to adopt than in legacy projects like an OFBiz… => The change of the build tool for OFBiz would be a fundamental change, particularly for upgrading existing installations. So a change to the project structure could be a deathblow to OFBiz vendor imports in customer projects. I think it could be a good starting point to look at Gradle and see if there is a wise way to use the strength and new features of a modern build tool without the need to turn things inside out in OFBiz. Martin Becker ecomify GmbH > Am 17.04.2015 um 13:56 schrieb Jacques Le Roux <jacques.le.r...@les7arts.com>: > > Le 17/04/2015 12:49, Jacopo Cappellato a écrit : >> On Apr 17, 2015, at 4:39 AM, Taher Alkhateeb <slidingfilame...@gmail.com> >> wrote: >> >>> Hi All, >>> >>> Thank you for your work but I thought we are more inclined to move to >>> gradle based build systems given its many advantages as a full programming >>> language build system based on groovy. >>> >>> Taher Alkhateeb >> I agree: we could explore the switch to Gradle and also review the way our >> source files (Java, Groovy and Minilang/xml) are organized (we could >> actually follow the layout that is considered the default for Maven and >> Gradle and possibly other tools). >> >> Jacopo >> > > I don't know if Gradle is stable now, but I'd surely be for instead of Maven. > If ever we really desire to move from Ant, I don't clearly see the necessity > at this stage... > > Jacques >
