On May 24, 2017, at 9:38 AM, Christofer Dutz <[email protected]> wrote: ... Regarding the build system … what is the projects general opinion on a Maven build? I know that Ant and Gradle are a lot more flexible as Maven, but I think it is a good thing that Maven is this strict, as it forces the developers to address structural issues instead of using workarounds. Especially in Open-Source projects with a lot of different levels of build system expertise I usually always had problems with non Maven builds. But this is just a general question without having seen the current state ----------------
I think we headed down the gradle path because someone stepped up and contributed an initial set of gradle build files. And it was simple. But it omitted building javadoc, release bundles, the jar manifest class-path that I’ve mentioned, and maybe some additional stuff (oh, like building java7 based jars using retrolambda, as well as building for an android tgt). I don’t know that the project has an overall position on gradle vs maven. Folks? I don’t have a strong opinion (though I was happy to see the elimination of an xml based build spec :-) Once “forced to address structural issues instead of using gradle workarounds", might one then end up with an equivalently simple/clean gradle based system? Though the path to get to that point may be less clear :-) — Dale
