++1
Regarding Gradle vs Maven, no strong opinion, let’s not start a Gradle vs Maven battle here :) I think maven is still more popular so it means more developers know it. Maven is fast enough I think since parallelism was introduced. Maven seems to me more documented. Still, the volunteer here to do it, should be the decider. I don’t know much gradle, but always happy to learn new things. The only concern for me is not complexifying versions comparisons, so if layout can be kept as is, it would be great, so I think here gradle is a better candidate. Regards On Wednesday, February 20, 2019, Vladimir Sitnikov < sitnikov.vladi...@gmail.com> wrote: > Hi, > > I think it is a good time to migrate build system to Gradle. > > Can you please express your opinion on that? > > If you struggle what to say, you might find the below options useful: > > [ ] ++1: 'Wow! I like this! Let's do it!' > [ ] +1: 'Let's do it!' > [ ] +0.9: 'This is a cool idea and i like it' > > > Philippe> No reason except time and volunteers. > Philippe> If you’re willing to do it, I’ll be more than happy . > > What I do remember is: > 1) "Maven is slow, so repeated builds would be very slow" > 2) "Maven is bad for highly customized cases like JMeter". > > I'm not sure if there are other points, so feel free to add. > > #1 is very true since Maven builds modules one by one with no > parallelism in mind. Maven is quite slow to startup and parse build > configuration as well, and it is bad at incremental builds. > > However, Gradle has parallelism in mind, and Gradle has daemon mode > (which is enabled by default), so repeated builds are super-fast. In > fact, it would probably be faster than current Ant build. > > #2 is true as well. Maven configuration is a bit of a pain when you > build non-trivial jar/tar structure. > Gradle however allows to resort to "shell command" or things like > that, so it should simplify things. > > I'm one of pgjdbc maintainers (PostgreSQL JDBC driver), and a couple > of years ago there was migration to Maven. > It did simplify things, however I would recommend going with Gradle > rightaway. > > Felix> We have one long standing contribution that we didn't integrate > (yet) > Felix> from Emilian Bold. He started to migrate the layout of our source > code > > I think we should be just fine to migrate in a single go. > In my experience, you can't predict the desired Gradle layout. > If we do multiple relayouts, it would just disturb people workflows > multiple times. I don't think it is a good idea anyway. > > Vladimir > -- [image: logo Ubik Ingenierie] <https://www.ubik-ingenierie.com> Philippe Mouawad Senior Performance Expert 320914981 <+33320914981> | p.moua...@ubik-ingenierie.com [image: ubik-ingenierie.com] ubik-ingenierie.com <https://www.ubik-ingenierie.com> | [image: 03.20.91.49.81] 03.20.91.49.81 <+33320914981> | [image: 23 rue du chemin de fer , 59100 , Roubaix] 23 rue du chemin de fer, 59100, Roubaix <https://www.openstreetmap.org/#map=18/50.69454/3.16455>
