James wrote:
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.
In fact I do. Unfortunately I am not well versed in how to
participate in such a project. I don't know where to start.
I checked out the maven-eclipse-plugin to see how they were doing
things and I don't think that it would be particularly hard to use
that code to do the same thing for m2eclipse.
I was actually referring to doing that from the IDE.
This is a wrong mailing list if you want to hack maven-eclipse-plugin. :-)
We have new Maven Project Wizard. You can model new functionality
along similar lines. Possible scenario could look like this:
-- Select pom.xml (or a starting folder to scan trough for pom.xml's)
-- Specify if project should be imported as a single project or separate
projects for modules
-- create separate projects for modules checkbox
-- copy to workspace checkbox (similar to import java projects in jdt)
Also note, that where possible you should be using Eclipse API,
especially for resources and projects in Eclipse workspace and should
not be creating .project and .classpath files. That makes easier to deal
with resource changes in Eclipse and eliminates need in explicit refreshing.
regards,
Eugene
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
