Hi Yeah that can be an idea. I assume this is for developers from the command line? CI servers etc will still use the maven version they have been instructed in their jobs.
We may also consider bumping up the lowest Maven version number that we have in the root pom as the pre-requisite. Its 3.2.5 currently, but maybe 3.3.3 can be an upgrade after the 2.19.0 release. On Sat, Apr 22, 2017 at 1:01 PM, Zoran Regvart <zo...@regvart.com> wrote: > Hi Claus, > > On Sat, Apr 22, 2017 at 10:14 AM, Claus Ibsen <claus.ib...@gmail.com> wrote: >> Anyone tried using the new Maven 3.5.0 and build the Camel source code >> with that. And if so any feedback? > > I've used it when testing Java 9 issues (using > docker.io/maven:3.5.0-jdk-9), worked without issues. > > Perhaps we should consider using Maven Wrapper[1] so that we all use > the same Maven version and create .mvn/maven.config and > .mvn/jvm.config[2] with some sane defaults? > > zoran > > [1] https://github.com/takari/maven-wrapper > [2] > https://maven.apache.org/docs/3.3.1/release-notes.html#JVM_and_Command_Line_Options > -- > Zoran Regvart -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
