Uploaded image for project: 'Maven Wagon'
  1. Maven Wagon
  2. WAGON-449

CLIENT not changed after setting PoolingHttpClientConnectionManager

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

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 2.8, 2.9, 2.10
    • 2.12
    • wagon-http
    • None

    Description

      The AbstractHttpClientWagon class statically creates both a PoolingHttpClientConnectionManager and a client that uses said connection manager. This is fine, had it not been the case that the client itself is a final field and is never updated.

      Thus, using setPoolingHttpClientConnectionManager has no effect as the client is based on the PoolingHttpClientConnectionManager created at startup. This affects users that e.g. may want to change the SSLContext to support self-signed certificates.

      Attachments

        Activity

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

          People

            olamy Olivier Lamy
            jeannikl@hypirion.com Jean Niklas L'orange
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Issue deployment