When you do the Import -> General -> Maven project when you have the m2eclipse
thing installed there are several disadvantages:
1) As you mentioned, things like PermGen and other flags in MAVEN_OPTS are
ignored.
2) m2eclipse actually runs "mvn", thus, the default profiles are used. In
our
gt;>> Maven
>>> plugin apparently does not allow you to set MAVEN_OPTS parameters (it
>>> seems
>>> to ignore the already set environment variable for it), causing
>>> out-of-memory errors compared to running Maven from the command line. Am
>&
t;> Maven
>> plugin apparently does not allow you to set MAVEN_OPTS parameters (it
>> seems
>> to ignore the already set environment variable for it), causing
>> out-of-memory errors compared to running Maven from the command line. Am
>> I
>> largely correct
MAVEN_OPTS parameters (it seems
> to ignore the already set environment variable for it), causing
> out-of-memory errors compared to running Maven from the command line. Am I
> largely correct here?
>
> Thanks,
> Glen
>
> [1] http://cxf.apache.org/setting-up-eclipse.html
&g
Maven from the command line. Am I
largely correct here?
Thanks,
Glen
[1] http://cxf.apache.org/setting-up-eclipse.html
--
View this message in context:
http://www.nabble.com/Using-the-Eclipse-Maven-plugin-for-CXF-tp20832510p20832510.html
Sent from the cxf-dev mailing list archive at Nabble.com.
