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
