Community
Participate
Working Groups
I have flat project structure, all projects exist at the same level in the directory in including the maven parent, but in this directory there is also a pom.xml which is a multimodule pom, to facilitate building the whole application with one command. ./myparentproj/pom.xml ./myliba/pom.xml ./mylibb/pom.xml pom.xml When i have this open as 4 projects, I have the multi-module pom.xml open as a project so that I can edit the pom.xml and commit atomically, but i add filters to the multimodule project to ignore the child projects, otherwise: - all the files show up twice in the resource browser - all the launch files show up twice in run/debug - all the files show up twice in team synchronise and it's get very confused. But when i right click on a project and Maven -> Update Dependencies… or Maven -> Update Project Configuration… it does not show any projects at all. If I close the multimodule project, now the update project configuration dialog shows everything. (but now i can't do atomic commits) If I keep the project open but remove the resource filters, it works too. (but now everything shows up twice in eclipse) Attached is a workspace / maven project tree which demonstrates the problem. Open the workspace testMvn, right click on test-libA, Maven -> Update Dependencies... and the dialog shows no project to update.
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
Moved to https://github.com/eclipse-m2e/m2e-core/issues/
