Bugzilla – Full Text Bug Listing
| Summary: | Workspace resolution doesn't find newly opened projects | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Rich Seddon <rseddon> | ||||
| Component: | m2e | Assignee: | Project Inbox <m2e.core-inbox> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | digulla, igor, stephen.brandwood | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Mac OS X - Carbon (unsup.) | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
Should be fixed now. http://git.eclipse.org/c/m2e/m2e-core.git/commit/?id=883bfbc812ffce68a7587c00627ec417e43815a8 https://github.com/sonatype/m2e-core-tests/commit/9d2f2305cbba3f95564094a454d6928fb7686d85 Forgot to mention, workaround is to Maven->UpdateDependencies on the projects being opened. I have the same problem even after updating to 1.0.100.201107060301. I have three project A, B, C. A depends on B depends on C. All three are open. I close B and C. Then I open B again. Before the update 1.0.100, I would get an error in "B" that C is missing. A would have no error but B would be resolved from the local repo and not from the workspace. With 1.0.100, I get an error in "A" that "C" is missing but "B" is happy now. Invoking "Maven->Update Dependencies..." on the broken project solved the problem. Then I closed B. That gave me an error in A saying that "B" is missing. At this point, "Update Dependencies" didn't do anything. There are more projects in my workspace which depend in B but those did the switch. It seems this doesn't happen for all projects but only for some. Damn. I just noticed that I actually had the project B as a Java project dependency in B (it was in the .classpath). Please ignore my last report; I'll come back if I get the error again. *** Bug 353082 has been marked as a duplicate of this bug. *** *** Bug 350777 has been marked as a duplicate of this bug. *** |
Created attachment 198982 [details] Sample project. Newly opened projects are not detected as workspace dependencies. Sample attached. 1) Import the proejcts into M2E, observe that "bar" shows up as a workspace dependency of "foo". 2) Select "bar", and run a maven install. 3) Close "bar" Observe that the "bar" dependency of "foo" is now resolving to the artifact in the local maven repository. 4) Open "bar" The "bar" dependency of "foo" is incorrectly resolving to the local maven repository. It seems the only way to fix this is to run a full build.