| Summary: | update project configuration / dependencies does not show any project when nested projects are hidden | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | dan carter <dantheperson> | ||||
| Component: | m2e | Assignee: | Igor Fedorenko <igor> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | igor, matthew, sflaniga | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
dan carter
Maybe I'm not following your steps in exactly the same way, but I have existing projects in my workspace as you've described, and adding resource filters doesn't prevent m2e from populating the dialog. (In reply to comment #0) > > > Attached is a workspace / maven project tree which demonstrates the problem. > Did you forget to attach the example project? Seems to be a project with the workspace, when i open on another machine it says the test-libA/.project is missing, although it is there! Let me try again. Hrm, and the attachment failed to upload anyway! Created attachment 210190 [details]
maven project tree
mkdir newworkspace/
cd newworkspace/
tar xvfj ../test-aggregator.tbz
open newworkspace as an eclipse workspace
File -> Import -> Maven -> Existing Maven Projects
select test-aggregator -> (leave all 3 selected ) -> Finish
Right click test-libA -> Maven -> Update Project Configuration
no projects displayed.
(In reply to comment #1) > Maybe I'm not following your steps in exactly the same way, but I have existing > projects in my workspace as you've described, and adding resource filters > doesn't prevent m2e from populating the dialog. Please try the attached project, now that i've finally attached successfully. (In reply to comment #1) > Maybe I'm not following your steps in exactly the same way, but I have existing > projects in my workspace as you've described, and adding resource filters > doesn't prevent m2e from populating the dialog. Also, If you do have a similar setup that allows nested maven projects, where the filesystem represents the maven project hierarchy, and you do not suffer the duplicated resource issue, nor the issue i mention in this report, then i would be interested to know how you have your eclipse workspace setup. Should be fixed now. http://git.eclipse.org/c/m2e/m2e-core.git/commit/?id=aa4ac7a3cc0e93524a0503310de2907cf36a386f |