I have created a PR for the Maven wrapper [1] targeting the master branch and using Maven 3.5.2.
Thanks, Gregor [1] https://github.com/apache/camel/pull/2083 On Tue, Nov 7, 2017 at 10:16 AM, Zoran Regvart <zo...@regvart.com> wrote: > Hi Gregor & Cameleers, > yeah I think we should add Maven Wrapper, I think it's good to have as > much project related tools/scripts within source control. > > Some time ago I started experimenting on how to make the build faster > on Jenkins and I created a branch[1] to experiment with on my GitHub > fork. I was also testing incremental compile/test support by various > Maven extensions. > > Unfortunately as with most my ambitions I found no time to bring to fruition > :( > > zoran > > [1] https://github.com/zregvart/camel/commits/jenkinsfile > > On Tue, Nov 7, 2017 at 10:02 AM, Gregor Zurowski > <gre...@list.zurowski.org> wrote: >> Hi Zoran, >> >> Thanks for digging into this. >> >> What do you think about using the Maven Wrapper for Camel going >> forward? This way we could manage the Maven version from within the >> project itself and even use the correct Maven version per branch / >> Camel release (via the maven-wrapper.properties file). >> >> Thanks, >> Gregor >> >> On Tue, Nov 7, 2017 at 1:01 AM, Zoran Regvart <zo...@regvart.com> wrote: >>> Hi Cameleers, >>> I'm running a Jenkins instance to build Camel, and we have been >>> experiencing memory issues similar to those we have on >>> builds.apache.org. I've analysed a heapdump and traced it back to >>> Maven issue MNG-6030[1]. >>> >>> I see that Camel.2.19.x.fulltest and Camel.2.19.x.notest jobs are >>> running with Maven 3.3.3. I think those should be upgraded to at least >>> 3.5.0. >>> >>> zoran >>> >>> [1] https://issues.apache.org/jira/browse/MNG-6030 >>> -- >>> Zoran Regvart > > > > -- > Zoran Regvart
