Community
Participate
Working Groups
Whenever you have imported an existing maven project B which lies below your already existing maven project A (due to A being a multimodule project and B being a module of A), the reference to this project is stored as absolute path. This leads to problems if you move the whole workspace, because then only the original project A is found but not B, because the given absolute path does not exist anymore. Please always import projects with relative paths to prevent this behaviour. This does also occur with the subversive-plugin when you checkout a complete multimodule maven project.
I am not sure I understand what you mean. Can you please provide exact steps to reproduce the problem?
Here are the steps to reproduce: 1. Import a multimodule maven project into a clean Eclipse workspace 2. The root project and all submodules are correctly imported as separate projects within Eclipse. 2. Close Eclipse 3. Move the workspace folder to another location 4. Open the moved workspace in Eclipse What you see is, that only the top project can be found anymore. This is due to the location of all other projects are given as absolute paths, although they should have been given as relative workspace paths, since the projects are within the workspace. You can easily check by looking at the .metadata/.plugins/org.eclipse.core.resources/.projects/<projectname>/.location file within the workspace folder. There an absolute path is given.
Discovered this today and happy that this bug report already exists. Use case: Before we converted our project to a multi-module maven project, it was very easy to backup the Eclipse workspace, e.g. when testing Eclipse/Eclipse-plugins upgrades (shared Eclipse installation for many developers). Now that is not possible anymore.
closing old/stale bugreports
Moved to https://github.com/eclipse-m2e/m2e-core/issues/
