No, it is just a guidance principle, where we do/use whatever suits us and not what other people do/use.
In a way, what you are suggesting would "prevent innovation" since no one would ever use something new. ;-) We would still all be on the single Mainframe that rules the world... And personally, I am seldom upset with Gradle, and Maven often breaks expectations in larger projects. Maven's main feature is to get started quickly, but Gradle is sort of beating Maven at that too. Anyway, we won't move back to Maven for the build system. That would require some outstanding argument. And for this tool about getting started with Qi4j, I do want to support (eventually) that people can generate Maven or Gradle (possibly others) projects for themselves, and I just realized that this is probably what you are arguing for... On Sat, Apr 25, 2015 at 8:15 AM, James Carman <[email protected]> wrote: > So, your build tool would have prevented innovation? > On Fri, Apr 24, 2015 at 8:09 PM Niclas Hedhman <[email protected]> wrote: > > > We had this discussion 4-5 years ago.... Qi4j wouldn't exist if we wanted > > "mainstream and supported" ;-) LOL > > > > > > > > On Sat, Apr 25, 2015 at 7:30 AM, James Carman < > [email protected]> > > wrote: > > > > > I would recommend against gradle. Maven is far more mainstream and > > > supported. > > > On Fri, Apr 24, 2015 at 7:20 PM Niclas Hedhman <[email protected]> > > wrote: > > > > > > > Yeah, Gradle is awesome, and I ran into Hans Dockter back in 2009 and > > > after > > > > 4 days in the same room (DDD Immersion course), he got me convinced > > and I > > > > think Qi4j moved to Gradle in 2010... > > > > > > > > On Sat, Apr 25, 2015 at 2:02 AM, Roman Shaposhnik < > > [email protected]> > > > > wrote: > > > > > > > > > On Fri, Apr 24, 2015 at 12:59 AM, Sandro Martini > > > > > <[email protected]> wrote: > > > > > > Hi Niclas, > > > > > > I think it's a good idea, Gradle is really a powerful tool !! > > > > > > > > > > A comment from a peanut gallery: I can't recommend Gradle > > > > > highly enough. > > > > > > > > > > > What do you think on implementing these features with Gradle > > plugins > > > ? > > > > > > Just for info, Grails 3 has been rewritten and all > > developer-related > > > > > > features are now on top of Gradle (with custom gradle plugins, to > > > make > > > > > > available shell commands and other developer-related stuff) so > > maybe > > > > > > something like this could be good even here ... > > > > > > > > > > That's what I was thinking (without being able to commit to > actually > > > > > doing anything along these lines :-(). > > > > > > > > > > Thanks, > > > > > Roman. > > > > > > > > > > > > > > > > > > > > > -- > > > > Niclas Hedhman, Software Developer > > > > http://zest.apache.org/qi4j <http://www.qi4j.org> - New Energy for > > Java > > > > > > > > > > > > > > > -- > > Niclas Hedhman, Software Developer > > http://zest.apache.org/qi4j <http://www.qi4j.org> - New Energy for Java > > > -- Niclas Hedhman, Software Developer http://zest.apache.org/qi4j <http://www.qi4j.org> - New Energy for Java
