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