I'm noticing a lower memory usage (compared to v3.0.2) when building the Cargo project (trunk), but can't find a jira ticket that would explain this. Is this expected (not that I'm complaining)? All plugin versions are pinned and this is a clean build. I tested it several times, and the same result.
With Maven 3.0.2: 79M/265M With Maven 3.0.3-RC1: Final Memory: 60M/265M The build time seems to be slightly longer though. Not that much, just a few (5-10) secs on a 5+ min build. mvn -v: Apache Maven 3.0.3-RC1 (r1074308; 2011-02-24 22:41:17+0100) Maven home: /usr/local/maven Java version: 1.6.0_22, vendor: Apple Inc. Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home Default locale: en_US, platform encoding: MacRoman OS name: "mac os x", version: "10.6.6", arch: "x86_64", family: "mac" /Anders On Thu, Feb 24, 2011 at 22:57, Benjamin Bentmann <benjamin.bentm...@udo.edu>wrote: > Hi, > > we're aiming at a bugfix release of Maven 3 in the next week and > following tradition we invite interested users in taking the RC for a > test drive in order to detect and fix potential regressions since > version 3.0.2 before the actual release of 3.0.3. > > For the duration of the RC testing, sources and binaries are staged at: > > https://repository.apache.org/content/repositories/maven-049/org/apache/maven/apache-maven/3.0.3-RC1/ > > As usual, the changes since the previous release are listed in JIRA: > > http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=17061 > > Thanks, > > > -The Maven Team > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >