For new modules I usually do Right-click on the parent project, Import->
Maven Projects. The import wizard comes preconfigured to import new
modules, so I only need to press Finish.
For deleted modules... Subclipse leaves empty projects after
Team->Update, so I just delete those.
Obviously not ideal, but I put it into "good enough for now" bucket ;-)
Oh, and I usually do Team->Update on the parent project only.
--
Regards,
Igor
David C. Hicks wrote:
Hi folks,
I wonder if anyone has any pointers or tips that might be helpful in
this situation.
We have a multi-module Maven project that we work with in Eclipse.
Checking the code out of Subversion using the M2Eclipse plugin is
great! We end up with an Eclipse project for each of the POM files
(parents, sub-modules, etc.). The problems begin when the "structure"
of the project changes - ie. a new module is added, one is removed,
etc. The only reliable way of getting our development environment back
to a working state that we've found is to blow away the entire set of
projects in Eclipse and check them all back out again.
Is there a better way to handle these kinds of changes?
Thanks,
Dave
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
