Uploaded image for project: 'Maven Surefire'
  1. Maven Surefire
  2. SUREFIRE-104

unable to establish my own http protocol handler for unit tests

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Won't Fix
    • 2.0 (2.2 plugin)
    • None
    • None
    • None
    • jse 5.0 (osx)

    Description

      In order to establish my own http protocol handler, I set the system property java.protocol.handler.pkgs and ensure that the tests require a fork. The test runs fine under maven 1.0.2, but fails under maven 2.0.4. I have tried both surefire 2.1.3 and 2.2, and both with the childDelegation option.

      The test sees the system property properly set, but the test's protocol handler is not actually used.

      The attached zip file demonstrates this problem (run "maven test" and "mvn test").

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            afyfe Andy Fyfe
            Votes:
            8 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment