[MPIR-376] LightweightHttpsWagon is always used

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0.0
• Fix Version/s: 3.0.1, 3.1.0
• Component/s: dependencies, dependency-management, plugin-management

Environment

Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe; 2018-06-17T20:33:14+02:00)
Maven home: /opt/apache-maven
Java version: 1.8.0_152, vendor: Oracle Corporation, runtime: /Library/Java/JavaVirtualMachines/jdk1.8.0_152.jdk/Contents/Home/jre
Default locale: de_DE, platform encoding: UTF-8
OS name: "mac os x", version: "10.13.6", arch: "x86_64", family: "mac"

• Assignee: Michael Osipov
• Reporter: Jan Gerken
• Created: 14/Sep/18 16:42
• Updated: 15/Dec/19 20:52
• Resolved: 20/Aug/19 16:23

Description

For all dependencies, one of the plugins needs to download always the LightweightHttpsWagon is used. Independent of the wagon provider configuration in the settings.xml or via -Dmaven.wagon.provider.https and -Dmaven.wagon.provider.http.

Starting with Maven 3.0.4 the httpclient is the default wagon provider used for http and https connections. Therefore, I added add httpConfiguration for all servers I access in my settings.xml to reduce the timeout. This works well with all other plugins but for this plugin in version 3.0.0 it generates the following warning for each download:

[WARNING] Could not apply configuration for central to wagon org.apache.maven.wagon.providers.http.LightweightHttpsWagon:Cannot find 'httpConfiguration' in class org.apache.maven.wagon.providers.http.LightweightHttpsWagon

I tried to explicitly define the wagon provider to be httpclient for each server in my settings.xml and I tried to force the client via the command line arguments. None of this changes was successful.

Please make this plugin use the configured wagon provider for each server and use the same default provider as the Maven version.