Is the Log4j version the ONLY thing that changed? I am guessing that more dependencies are being brought in perhaps.
You can run Maven with verbose/debug output and see what classpath the compiler is using in both cases. Gary On Fri, Nov 21, 2014 at 4:34 AM, Tomek Sztelak <[email protected]> wrote: > Hello > > We just updated log4j from 2.0-beta9 to 2.1 and memory consumtion during > compilation of our application increased about 300-400MB causing > OutOfMemory on same machines. > Any idea what can cause this? > > Best regards. > -- E-Mail: [email protected] | [email protected] Java Persistence with Hibernate, Second Edition <http://www.manning.com/bauer3/> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/> Spring Batch in Action <http://www.manning.com/templier/> Blog: http://garygregory.wordpress.com Home: http://garygregory.com/ Tweet! http://twitter.com/GaryGregory
