[MNG-4254] Support selection of wagon implementation for a particular protocol

• Type: Improvement
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 2.2.0
• Fix Version/s: 2.2.1
• Component/s: Artifacts and Repositories
• Assignee: John Dennis Casey
• Reporter: John Dennis Casey
• Created: 23/Jul/09 13:06
• Updated: 06/Apr/15 01:53
• Resolved: 23/Jul/09 20:08

Description

We have competing bug lists in the different implementations of the HTTP wagon, so it'd be nice to provide a default (lightweight) wagon implementation, then allow users who need it to specify the httpclient-driven implementation via Maven configuration.

This is implemented for Maven 2.2.1, just needs integration tests.

Issue Links

• is related to: WAGON-334 Add provider specific role hints to HTTP wagon component descriptors
• relates to: MNG-4228 [regression] Authorization failed: Not authorized by proxy.
• relates to: MNG-4235 [regression] Maven 2.2.0 produces invalid checksums during deployment to secured HTTP repo
• relates to: MNG-4236 [regression] http wagon uploads files twice with Maven 2.2.0 when preemptive auth is disabled (default setting)
• relates to: MNG-4279 wagon provider selection should fail gracefully and use protocol for roleHint if protocol-provider roleHint isn't available.
• relates to: MNG-5175 replace wagon http lightweight with wagon http 2.1