Quoting: 'why change in the first place'. That is one of the most important question, perhaps even 'the most important'.... And it seems, that one isn't answered to the fullest.
I like: if it aint broken, don't try to fix it'. But also 'a square peg doesn't fit in a round hole'. Is our current build mechanism broken? Is our current mechanism a square peg? But beyond that: have we fully explored the all/other paths? We currently have following options: Ant+IVY, Groovy/Gradle, Maven. They are all 'build' solutions (at least according to their sites, but the writers of any of those pages could be disregarded as experts). But there are also Apache Buildr and Continiuum, according to this site listing options: http://en.wikipedia.org/wiki/List_of_build_automation_software. Should we explore inviting the real experts (those of all these tools) to share their insights, so that we can base the decision on real information than just conjecture/limited experiences? And on another and related aspect: how much effort would the benefit of each option require to have it fully operational for OFBiz? That should help determination too. Best regards, Pierre Smits *ORRTIZ.COM <http://www.orrtiz.com>* Services & Solutions for Cloud- Based Manufacturing, Professional Services and Retail & Trade http://www.orrtiz.com On Mon, Apr 20, 2015 at 7:00 PM, David E. Jones <[email protected]> wrote: > > That gets back to the question of why change in the first place... build > files may be smaller and easier to maintain, but there may not be a good > reason! > > -David >
