Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 335115

Summary: Child module not handled correctly when using flat structure
Product: z_Archived Reporter: Martin Ackermann <public.viewing>
Component: m2eAssignee: Project Inbox <m2e.core-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: minor    
Priority: P3 CC: igor, m.turra, public.viewing
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:
Attachments:
Description Flags
Example project
none
Screenshot showing the error none

Description Martin Ackermann CLA 2011-01-23 10:01:37 EST
Created attachment 187381 [details]
Example project

When aggregating projects on two levels, m2eclipse does not show the leaf project correctly in the package explorer and in the navigator. See attached screenshot and example project. I use "Check out as Maven Project..." to retrieve the project structure from SVN.

trial-maven is the parent project. trial-maven-product is its child module. trial-maven-child-module is a child module of trial-maven-product, residing on the same directory level as trial-maven-product.

trial-maven-child-module has a src folder with content. But in eclipse, the src folder is only shown under the node trial-maven, not under the node trial-maven-child-module.

m2eclipse 0.12.1, Eclipse Galileo SR2, Windows XP SP3
Comment 1 Martin Ackermann CLA 2011-01-23 10:02:34 EST
Created attachment 187382 [details]
Screenshot showing the error
Comment 2 Martin Ackermann CLA 2011-01-23 10:03:26 EST
As I detected now: The reason is, that .project and .settings are generated under maven.1295720474546\trial-maven-child-module. The should be generated under trial-maven\trial-maven-child-module.
Comment 3 Martin Ackermann CLA 2011-01-27 13:25:32 EST
The cause of the problem is not the multi-level aggregation. It's the flat structure between trial-maven-product and trial-maven-child-module.
Comment 4 Igor Fedorenko CLA 2011-01-31 22:17:59 EST
I am not able to reproduce the problem using provided sample project. Tried both 0.12.1 and latest 0.13.0 from master on Linux. Also tried 0.12.1 on WinXP. Feel free to reopen the problem with exact steps to reproduce
Comment 5 Martin Ackermann CLA 2011-02-01 14:11:38 EST
Thanks for trying to reproduce.

Here are the exact steps:
- Download example project above and unzip.
- File->Import...->General->"Existing Projects into Workspace". "Browse..." to the parent directory of the unzipped project. Select trial-maven. Check "Copy projects into workspace". "Finish".
- In the package explorer, right-click on trial-maven and execute Team->"Share Project...". "SVN" and "Next >". "Use existing repository location" and "Next >". "Use project folder as name" and "Finish".
- In the team synchronizing perspective "Commit All Outgoing changes". Deselect .project (3 times), .settings (3 times), .classpath (1 time) and "OK".
- In the package explorer, right-click on trial-maven and execute "Delete". Check "Delete projects on disk" and "OK". Exit the dialog with Titel "Refactoring" (showing an exception) with "Abort". Repeat right-click on trial-maven and execute "Delete". Check "Delete projects on disk" and "OK". 
- In the SVN repository exploring perspective, right-click on trial-maven and execute "Check out as Maven Project...". Let "Check out All projects" activated and "Finish".

This produces the error, at least in my eclipse configuration and in my workspace. Let me know if you still cannot reproduce, then I will try with a fresh installation and a fresh workspace.
Comment 6 Igor Fedorenko CLA 2014-04-23 18:02:08 EDT
Closing stale bugreports
Comment 7 Denis Roy CLA 2021-04-19 13:25:37 EDT
Moved to https://github.com/eclipse-m2e/m2e-core/issues/