Maven 2 & 3

webdav does not set http-proxy correctly

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 2.0.9
  • Fix Version/s: 2.1.0-M1
  • Component/s: None
  • Labels:
    None
  • Complexity:
    Intermediate
  • Number of attachments :
    2

Description

patch is attached to WAGON-82 (0001-Make-the-artifact-manager-using-wagons-ProxyInfoProv.patch), utilising the new APIs in beta-3

Attachments

  1. Text File
    MNG-3599.patch
    27/Jul/08 11:59 AM
    2 kB
    Brett Porter
  2. Text File
    webdav.log
    28/Oct/08 10:47 AM
    3 kB
    Benjamin Bentmann

Issue Links

This issue relates to:
MNG-4211 [regression] proxy access broken between maven version 2.0.10 and 2.1. Probably due to addition of wagon 1.0-beta-4+ Blocker Closed
This issue depends upon:
WAGON-225 proxyInfoProvider is never used Major Closed
MNG-3622 upgrade to wagon 1.0-beta-4 Major Closed

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Brett Porter added a comment -

there's a bug in wagon so this needs to be postponed

Show
Brett Porter added a comment - there's a bug in wagon so this needs to be postponed
Hide
Permalink
Brett Porter added a comment -

attached patch to be used once wagon can be upgraded (supercedes WAGON-82 patch)

Show
Brett Porter added a comment - attached patch to be used once wagon can be upgraded (supercedes WAGON-82 patch)
Hide
Permalink
Benjamin Bentmann added a comment - - edited

The correspondig IT indicates that this is in principle also fixed in 2.0.10 as expected from the SVN history. However, due to MNG-3805 the behavior is not reliable. The wrong dependency resolution picks commons-httpclient 3.0 instead of 3.1 which seems to cause a LinkageError while loading the WebDAV beta-3 wagon, which in turn causes fallback to the bundled beta-2 version.

Show
Benjamin Bentmann added a comment - - edited The correspondig IT indicates that this is in principle also fixed in 2.0.10 as expected from the SVN history. However, due to MNG-3805 the behavior is not reliable. The wrong dependency resolution picks commons-httpclient 3.0 instead of 3.1 which seems to cause a LinkageError while loading the WebDAV beta-3 wagon, which in turn causes fallback to the bundled beta-2 version.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.