I believe it should be fine, but first we need access to the CI. -- Andrea Cosentino ---------------------------------- Apache Camel PMC Member Apache Karaf Committer Apache Servicemix PMC Member Email: ancosen1...@yahoo.com Twitter: @oscerd2 Github: oscerd
On Tuesday, November 7, 2017, 1:01:40 AM GMT+1, 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
