cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Glen Mazza <>
Subject Re: Using the Eclipse Maven plugin for CXF
Date Thu, 04 Dec 2008 13:16:43 GMT

Oh no--I wasn't suggesting it as an alternative, but just to document it as a
warning/advisement, and just wanted to make sure I was reasonably accurate
in my assessment.


Benson Margulies-4 wrote:
> I have no trouble with IDE builds, debugging, etc when I run our
> existing procedure and importing the resulting projects into eclipse.
> Some time ago I tried the maven plugin for Eclipse and got some pretty
> sorry results (not with CXF). By all means document it as an
> alternative, but not to replace.
> On Thu, Dec 4, 2008 at 7:32 AM, Glen Mazza <> wrote:
>> Hi, I would like to update our Eclipse setup page[1] with additional
>> info.  I
>> noticed that instead of using mvn eclipse:eclipse command (or the
>> -Psetup.eclipse parameter described on that page), there is an Eclipse
>> menu
>> File -> Import -> General -> Maven Projects option (at least for Eclipse
>> IDEs that have the Maven plugin installed), which works just by choosing
>> the
>> root directory of the CXF download.
>> As I can see, the advantage of importing CXF as standard Eclipse projects
>> (i.e., mvn eclipse:eclipse) over importing as a Maven project is that
>> IDE-builds, debugging and code-completion, etc. is not as good or even
>> available with the Maven project import option.  Also, the Eclipse's
>> 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 here?
>> Thanks,
>> Glen
>> [1]
>> --
>> View this message in context:
>> Sent from the cxf-dev mailing list archive at

View this message in context:
Sent from the cxf-dev mailing list archive at

View raw message