Fancy to contribute this?
MNGECLIPSE-183: Allow the selection of a POM in the local file system to
setup the project in Eclipse
http://jira.codehaus.org/browse/MNGECLIPSE-183
Also note that you can also a) run "Update Sources" action that would
clean unneeded dependencies; b) import whole codebase as a single
Eclipse project.
regards,
Eugene
James wrote:
Wow. I've really been able to use this plugin since 0.10. There is
one thing I am wondering though.
I have a project with 20 or more maven subprojects (modules
whatever). Right now I have two choices to set up for use with the
m2eclipse plugin.
1. Use the mvn eclipse:eclipse command then import projects in to
workspace, enable maven on all projects, delete the dependencies
created from the eclipse:eclipse command so the Maven2 Dependencies
won't collide with the eclipse:eclipse created dependencies.
2. Painstakingly set up an eclipse project for each module, then
enable the m2eclipse plugin for all projects.
Neither seems to be ideal.
Wouldn't it be great if there was a command like eclipse:eclipse that
just went through all your sub modules and set up the correct .project
and .classpath entries for the m2eclipse plugin? Then one big import
later... voila... productivity.
Keep up the good work.
-James
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
