No issue with multi threads build ? see
https://jira.codehaus.org/browse/MCOMPILER-170
I have to say depending on os/jdk it may cause weird issue. I will try
to release a new version soon with the fix.
2012/5/12 Jörg Schaible :
> Hi Hilco,
>
> Hilco Wijbenga wrote:
>
>> Hi all,
>>
>> I have notice
Hi Hilco,
Hilco Wijbenga wrote:
> Hi all,
>
> I have noticed that in a fairly large reactor build the build dies
> close to the end (about 10 modules to go out of around 90). It simply
> runs out of memory. Restarting it with -rf allows it to finish without
> issues. There is a limit to how much
On 12 May 2012, at 12:05, Mark Struberg wrote:
> It could also be a proxy problem of course. How is guice doing proxies?
Maven currently uses guice-no_aop
http://code.google.com/p/google-guice/wiki/OptionalAOP so any proxies would use
the standard JVM proxy mechanism.
That said, I wouldn't exp
2012/5/12 Hilco Wijbenga :
> Hi all,
>
> I have noticed that in a fairly large reactor build the build dies
> close to the end (about 10 modules to go out of around 90). It simply
> runs out of memory. Restarting it with -rf allows it to finish without
> issues. There is a limit to how much memory
It could also be a proxy problem of course. How is guice doing proxies?
Proxies are also loaded via the ClassLoader and consume perm gen space.
LieGrue,
strub
- Original Message -
> From: Stuart McCulloch
> To: Maven Users List
> Cc:
> Sent: Saturday, May 12, 2012 11:36 AM
> Subje
On 12 May 2012, at 07:32, Hilco Wijbenga wrote:
> On 11 May 2012 22:47, Anders Hammar wrote:
>> This is not uncommon for large multi-module builds. You need to
>> increase the memory available for Maven, such as the heap depending on
>> the error you're getting.
>> Do this by setting the MAVEN_OP
