Hi All, Both Maven and Gradle are great build systems. Gradle is flexible and has a better performance than Maven. However, it adds some complexity to the project and requires to get familiar with its plugins. Maven could result in a painless transition than Gradle as a build system. Gradle-Kotlin DSL ( https://docs.gradle.org/current/userguide/kotlin_dsl.html) seems promising for solving some of the drawbacks of Gradle but I think that it needs time.
We can go with Maven (even Gradle is not a bad choice). Here are some related issues: https://issues.apache.org/jira/browse/NUTCH-2292 https://issues.apache.org/jira/browse/NUTCH-892 Kind Regards, Furkan KAMACI On Fri, Nov 30, 2018 at 8:21 AM Chris Mattmann <mattm...@apache.org> wrote: > Thamme worked on this…check where he left off… > > > > > > > > *From: *lewis john mcgibbney <lewi...@apache.org> > *Reply-To: *"dev@nutch.apache.org" <dev@nutch.apache.org> > *Date: *Thursday, November 29, 2018 at 1:13 PM > *To: *"dev@nutch.apache.org" <dev@nutch.apache.org> > *Subject: *Maven vs Gradle for Nutch Build System > > > > Hi Folks, > > Seb and I were talking build systems this week. I wanted to get a feel for > what we as a PMC would rather use for the next Nutch build lifecycle. > > Personall I've used Maven for many of y Java projects however I have also > really enjoyed working with Gradle. > > I would like t start working on the build system such that we can > streamline the Nutch release process. Also we've seen people request Nutch > plugins as Maven artifacts for some time. > > Any thoughts? > > Lewis > > > -- > > http://home.apache.org/~lewismc/ > > http://people.apache.org/keys/committer/lewismc >
