Details

    • Type: Sub-task Sub-task
    • Status: Resolved Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.0.0-alpha-1
    • Component/s: Transport
    • Labels:
      None
    • Environment:
      all
    • Number of attachments :
      0

      Description

      Branch off the 2.2 trunk, replace all the http/dav providers and pass ITs

        Activity

        Hide
        Oleg Gusakov added a comment - - 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
        Show
        Oleg Gusakov added a comment - - 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
        Hide
        Oleg Gusakov added a comment - - 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 !

        Show
        Oleg Gusakov added a comment - - 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 !
        Hide
        Oleg Gusakov added a comment - - 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.

        Show
        Oleg Gusakov added a comment - - 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.
        Hide
        Oleg Gusakov added a comment - - edited

        testit0119 turned to depend of the current settings.xml, fixed it by using a test settings.xml

        Show
        Oleg Gusakov added a comment - - edited testit0119 turned to depend of the current settings.xml, fixed it by using a test settings.xml
        Hide
        Oleg Gusakov added a comment -

        testit0063 was missing an explicit jre folder - fixed

        Show
        Oleg Gusakov added a comment - testit0063 was missing an explicit jre folder - fixed
        Hide
        Oleg Gusakov added a comment -

        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
        
        Show
        Oleg Gusakov added a comment - 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
        Hide
        Oleg Gusakov added a comment -

        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.

        Show
        Oleg Gusakov added a comment - 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.
        Hide
        Oleg Gusakov added a comment -

        Done

        Show
        Oleg Gusakov added a comment - Done

          People

          • Assignee:
            Oleg Gusakov
            Reporter:
            Oleg Gusakov
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: