I am using the same procedure. It works fairly well. The best part
(compared to Ant) is that both command-line Maven and Eclipse work
off of the same descriptor (pom.xml). At times the plugin gets
confused after command line changes to the local repository, but
source refresh and full workspace rebuild fix most issues.
Andrus
On Jul 21, 2006, at 11:59 AM, Bill Dudney wrote:
The M2 plugin for eclipse is cool and works fairly well. There is
an incompatibility between mvn eclipse:eclipse and the plugin. When
you do mvn eclipse:eclipse it fills the .classpath with references
to M2_REPO/foo.jar but the plugin knows and understands your
pom.xml file so all that is not needed. The way I manage it is to
mvn eclipse:eclipse then delete all the M2_REPO stuff then add the
M2 Library. Tedious until the plugin is updated (for all I know it
already is, I'm just to lazy to figure out how to fix it so if
anyone knows please let me know) but it works. And once you get the
setup done the plugin is really cool allowing you to add and manage
your dependencies etc.
http://m2eclipse.codehaus.org/
is the update site for the eclipse plugin.
