Bug 675865

Summary: maven 3.0.2 fails to build projects (regression since 3.0-5)
Product: [Fedora] Fedora Reporter: Bobby Powers <bobbypowers>
Component: mavenAssignee: Stanislav Ochotnicky <sochotni>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: rawhideCC: akurtako, java-sig-commits, sochotni
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-03-01 15:47:09 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
maven output none

Description Bobby Powers 2011-02-08 01:07:49 UTC
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

Comment 1 Bobby Powers 2011-02-08 01:09:26 UTC
* s/is getting pulled in/isn't getting pulled in properly/

Comment 2 Bobby Powers 2011-02-08 11:00:30 UTC
... 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.

Comment 3 Stanislav Ochotnicky 2011-02-08 11:48:11 UTC
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.

Comment 4 Stanislav Ochotnicky 2011-02-25 14:30:01 UTC
I found a problem in our maven. Remote repositories wouldn't work due to problems with code injection. I am working on this

Comment 5 Stanislav Ochotnicky 2011-03-01 15:46:58 UTC
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.