[Created] (MPIR-376) LightweightHttpsWagon is always used

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[Created] (MPIR-376) LightweightHttpsWagon is always used

JIRA jira@apache.org
Jan Gerken created MPIR-376:
-------------------------------

             Summary: LightweightHttpsWagon is always used
                 Key: MPIR-376
                 URL: https://issues.apache.org/jira/browse/MPIR-376
             Project: Maven Project Info Reports Plugin
          Issue Type: Bug
          Components: dependencies, dependency-management, plugin-management
    Affects Versions: 3.0.0
         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"
            Reporter: Jan Gerken


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:

{code:java}
[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{code}

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 Maven version.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)