Embedd mercury wagon into 2.2.0 trunk

Oleg Gusakov added a comment - 26/Sep/08 1:12 PM - edited Branch created: https://svn.apache.org/repos/asf/maven/components/branches/2.2.0-M1-MNG-3759 IT results as of now: Tests run: 204, Failures: 1, Errors: 4, Skipped: 0, Time elapsed: 890.754 sec <<< FAILURE! Results : Failed tests: testmng3652_UnConfiguredDAV(org.apache.maven.integrationtests.MavenITmng3652UserAgentHeader) Tests in error: testForkFromReport(org.apache.maven.integrationtests.MavenITmng3703ExecutionProjectWithRelativePathsTest) testmng3599useHttpProxyForHttp(org.apache.maven.integrationtests.MavenITmng3599useHttpProxyForWebDAV) testmng3599useHttpProxyForWebDAV(org.apache.maven.integrationtests.MavenITmng3599useHttpProxyForWebDAV) testit0119(org.apache.maven.integrationtests.MavenIT0119PluginPrefixOrder) testit0119 was failing before mercury, ignoring testForkFromReport relies on the wagon optional resourceExists call. This call is not implemented in mercury transport as it's been ddemed inefficient: implementing such call would require a HEAD HTTP request, and we could not imagine situation where we would use HEAD not followed by GET. Or better say, GET servers as a faster alternative as it combines the two together: a failure in GET is the same as failure in HEAD, but if GET goes through, it's fater than HEAD, followed by GET. I will ignore this test, unless there is strong disagreement working on the other 3 failed tests

Oleg Gusakov added a comment - 26/Sep/08 6:14 PM - edited testmng3652_UnConfiguredDAV fixed, problem was protocol: test supplies dav:http , mercury understands http . Added protocol translation to wagon-mercury. This translation probably belongs in Mercury itself ? Only two proxy tests to go !

Oleg Gusakov added a comment - 29/Sep/08 4:57 PM - edited Switched to core-it-suite tests. Down to two failing tests: Tests run: 196, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 1,447.123 sec <<< FAILURE! Results : Tests in error: testit0119(org.apache.maven.it.MavenIT0119PluginPrefixOrder) testit0063(org.apache.maven.it.MavenIT0063Test) Tests run: 196, Failures: 0, Errors: 2, Skipped: 0 testit0119 was failing before testit0063 is a newly obtained headache - nothing to do with wagons, a jar cannot be found in system scope. I will try them both on Linux, to see is my environment is hosed.

Oleg Gusakov added a comment - 29/Sep/08 6:30 PM - edited testit0119 turned to depend of the current settings.xml, fixed it by using a test settings.xml

Oleg Gusakov added a comment - 30/Sep/08 5:10 PM testit0063 was missing an explicit jre folder - fixed

Oleg Gusakov added a comment - 30/Sep/08 6:02 PM Backported un-uber jar from trunk All tests pass Tests run: 196, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1,544.385 sec Results : Tests run: 196, Failures: 0, Errors: 0, Skipped: 0

Oleg Gusakov added a comment - 03/Oct/08 12:22 AM After running tests with fresh local repo, I see it0031 failing. This IT deals with plugin alias remapping, so I strongly suspect it's not related to mercury wagon. I will try to confirm.

Oleg Gusakov added a comment - 06/Oct/08 4:31 PM Done