Question

Basically there is a project I am new to that uses maven. I have only used maven once before. Anyway, I’m using the m2eclipse plugin. The project is one root directory where all the modules are sub-projects. I checked it in as a maven project and it created all the sub-projects correctly, but it changed the names of all the directories.

I have no idea why it did this, but this causes a lot of issues. From this point forward the modules/projects can’t be updated. Neither normal synchronization nor “update maven” through the maven sub-menu works to update the project correctly. And I obviously can’t commit/share the projects anymore because the directory structure has changed.

So my question is what is the proper way to import the maven project from svn so that it doesn’t do this? I guess I also want to know WHY it does this? It causes so many issues, why rename them? I read somewhere that it’s being renamed to the artifact Id… but like I said, I don’t know why.

The alternative is to not use the m2eclipse plugin at all and instead utilize maven’s eclipse:eclipse command (I believe that’s the one). Is there no way to make this work?

Thank you for your help and knowledge,

-Asaf

Answer 1

I have a similar structure, except that in my case sub-projects live in separate repositories and are connected to the main one via svn:externals. I perform check outs by choosing Import -> SVN -> Project from SVN and once everything has been checked out – and only the main project shows up in Eclipse – I select Import -> Maven -> Existing Maven Projects.

At the end all my projects show up in Eclipse, no directory is modified, and version control works without problems.