Team, Within NiFi we went with the "oldest version of Maven we could fairly easily support" approach. I really wish we had not.
As a new project you have one shot to set some of the fundamentals down right such as the JVM you're tied to or the Maven build environment and such. I recommend, picking the most forward leaning one you think you'll need. It is really easy to install the latest version of Maven but it is really non-trivial if you're doing interesting things with Maven to maintain support over long periods of time for behaviors of older versions. I'd seriously recommend you take the latest Maven release and call that the Maven version. That is purely a recommendation. I'll help whatever path is the consensus. Thanks Joe On Fri, Jul 22, 2016 at 5:12 PM, Suneel Marthi <[email protected]> wrote: > Well most Apache projects r now at Maven >= 3.3.3. > > Spark is at 3.3.9. > > So why stick with 3.2.5 ? > > On Fri, Jul 22, 2016 at 5:10 PM, Tim Ellison <[email protected]> wrote: > >> My understanding is that the change to Java 8 was because earlier versions >> are now end of life, and Pirk's dependencies are moving to Java 8. >> >> What is the driver to move up to a later Maven version? >> >> I guess as a principle, specifying the lowest possible version of the >> project's dependencies in the supported range allows for the broadest range >> of target systems. >> >> On 22 July 2016 at 21:16, Suneel Marthi <[email protected]> wrote: >> >> > Travis presently is set up with Maven 3.2.5. Consider going with a >> minimum >> > of 3.3.3 for Pirk, most other projects are at maven 3.3.9. >> > >> > I have the change for that as part of the PR for Pirk-10. >> > >>
