You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by victropolis <vi...@gmail.com> on 2014/04/25 02:37:29 UTC
RE: ForkedBooter in 2.2.1 does not honor MAVEN_OPTS
Is there any downside to using <forkMode>never</forkMode>?
--
View this message in context: http://maven.40175.n5.nabble.com/ForkedBooter-in-2-2-1-does-not-honor-MAVEN-OPTS-tp5764410p5791911.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: ForkedBooter in 2.2.1 does not honor MAVEN_OPTS
Posted by Baptiste Mathus <bm...@batmat.net>.
Yes, it does not isolate your tests from your main maven build. So if for
example your tests require too much memory, the OOME will kill the whole
maven build.
BTW, as maven 2.x is in the title, you should be aware it's now
deprecated/end of life.
Cheers
Le 25 avr. 2014 03:22, "victropolis" <vi...@gmail.com> a écrit :
>
> Is there any downside to using <forkMode>never</forkMode>?
>
>
>
> --
> View this message in context:
> http://maven.40175.n5.nabble.com/ForkedBooter-in-2-2-1-does-not-honor-MAVEN-OPTS-tp5764410p5791911.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>