Hide Forgot
Created attachment 477541 [details] maven output Description of problem: maven3 can't find dependencies when starting off with a clean ~/.m2/repository. I was able to build the same project (b2-standards, a pom-only project containing required deps and repository info for other projects) with maven3, deleted the ~/.m2/repository, and then mvn3 is unable to build. So I imagine there is some dep somewhere that is getting pulled in? I will attach the output of $ mvn3 -e -X clean install I can provide the pom if its helpful, but I'll have to redact parts (contains passwords & maybe sensitive urls...) Version-Release number of selected component (if applicable): 3.0.2-1 How reproducible: always
* s/is getting pulled in/isn't getting pulled in properly/
... this might be a PEBCAK error. Installing maven-clean-plugin may have fixed it (although I'm not sure, our nexus instance is offline temporarily). Will update/close when I confirm it was simply my fault.
Thank you for reporting the bug and verifying. It's quite possible something stopped working with 3.0 -> 3.0.2 update, but unless you are using mvn-local, mvn3 should be behaving exactly like original apache maven tarball. Therefore if you think this is really a bug in our maven, try to verify your build works with original tarball.
I found a problem in our maven. Remote repositories wouldn't work due to problems with code injection. I am working on this
I found the exact problem. plexus-containers-1.5.4 generated incorrect component.xml for certain cases. Maven 3.0.2 started using certain code paths that made this bug visible. I updated plexus-containers, rebuild aether to fix its compoents.xml and I am working on getting updates into F-15 as well. Current rawhide already has maven-3.0.3rc1 that seems to work for me. I am closing this as fixed, but if you find problems persist feel free to reopen.