I have "chatted" with Hans about this before, but I think it needs raising a little more "formally".
There are many people out there with mixed C, C++ and Java systems. Currently most of them have a horrible mish-mash build system. Most of these people want to unify their builds into one. Where the bulk of the code is C or C++ they are coming to SCons but its Java support is poor. Most Java based systems don't have any C++ so the C and C++ support in Ant and Maven is more or less non existent -- the C/C++ Ant task is not at all good. So there is debate in SCons circles (and yes I am involved) on improving SCons support for Java. However without reimplementing Ant, Maven or Gradle, they are going nowhere. It may be that SCons does indeed reinvent everything in Ivy, Maven, Ant and Gradle, but I think that would be an error. So, I wonder if having an hybrid SCons/Gradle system could solve the problem. Instead of having one and only one build framework, have two. This solves the total mish-mash by having a structured two-component solution, but harnesses all that is out there -- the C, C++ and LaTeX goodness of SCons, and the Groovy and Java goodness of Gradle. Both SCons and Gradle have DAGs and both have APIs so it should be a question of creating adaptors to allow SCons to "call" Gradle and Gradle to "call" SCons. If the mixed Python/Groovy result is not acceptable then it means SCons is going to have to reimplement Gradle in Python. Just some thoughts. -- Russel. ==================================================== Dr Russel Winder Partner Concertant LLP t: +44 20 7585 2200, +44 20 7193 9203 41 Buckmaster Road, f: +44 8700 516 084 London SW11 1EN, UK. m: +44 7770 465 077
signature.asc
Description: This is a digitally signed message part
