New submodules do not show up as seperate projects

A similar issue occurs if a module is renamed or removed - and is a bit more tricky But just supporting new projects would be great.

I work around this by selecting the mother project and do Import -> Maven. I then select the same name template and most modules should be grayed out because of name conflicts. I then tick the one (new) module and import it.

The best would be for this to be done automatically or semi-automatically.. "New module detected.. do you want to import it..?" (could pop up with the wizard that remembers the selection of workset and name template etc. from the original import)

Stian, it is better to submit a separate bug report for renaming scenario. It is also seem related to subtasks of MNGECLIPSE-920

The workaround doesn't seem effective for me because although the new project is created, it doesn't seem to be associated with the parent correctly.

If I synchronise the parent with SVN, it doesn't update contents of the newly added module projects (except in the parent parent). This caught me out badly, thinking I'm looking at the latest repository contents after an update, then finding out I'm not (ouch!).

Incidently, I just used svn "relocate" on the parent from TortoiseSVN and saw the parent and original children relocate, but not the new modules.

Haven't had time to investigate more fully, but still looks very broken to me.

David, what do you mean "not associated with parent correctly"?

Note that your modules should be in the same hierarchy as parent, i.e. you should not checkout modules from svn into a different location and should instead update parent project and import missing modules from the parent's folder hierarchy. Also, it is quite possible that you need to refresh resources in both parent and all chinld projects after updating parent from svn.

Eugene,
The workaround looks valid. Discovered I'd used "Checkout Maven Projects from SCM" (on parent) to add new modules that time, instead of "Import->Maven"
Thanks, DM.