Bugzilla – Full Text Bug Listing
| Summary: | Refactor->move project into parent maven project | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Peter Platek <peterplatek> |
| Component: | Core | Assignee: | JDT-Core-Inbox <jdt-core-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | 4.6 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | stalebug | ||
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. |
Now that eclipse displays hieriarchial projects, I think it would be great to implement the refactor->move of projects into a parent project. In the scenario I encountered I created a new maven project, let's call it 'projectA' and later realized that I want to add another maven project 'projectB' which would be related to 'projectA'. Therefore I created a maven parent pom project 'parent' and later created a maven module 'projectB' which ended up being nested under 'parent'. At this point my Project Explorer shows this: projectA parent -projectB Now I would like to select 'projectA' and refactor->move it to 'parent', but at this point that is impossible from eclipse and I get: ${WORKSPACE_LOC}/parent overlaps the location of another project: 'parent' What should happen is the project gets moved under 'parent' and we end up seeing this: parent -projectA -projectB At the same time the 'parent' and 'projectA' pom.xml files should be updated to reflect the new hierarchy.