[jira] [Commented] (MPIR-376) LightweightHttpsWagon is always used
[
https://issues.apache.org/jira/browse/MPIR-376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16912198#comment-16912198
]
Hudson commented on MPIR-376:
-
Build succeeded in Jenkins: Maven TLP » maven-project-info-reports-plugin »
master #61
See
https://builds.apache.org/job/maven-box/job/maven-project-info-reports-plugin/job/master/61/
> 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
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.0.1
>
> Attachments: build.log, pom.xml
>
>
> 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 the Maven version.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (MPIR-376) LightweightHttpsWagon is always used
[
https://issues.apache.org/jira/browse/MPIR-376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1692#comment-1692
]
Michael Osipov commented on MPIR-376:
-
[~rfscholte], all ITs pass on Jenkins. I am going to merge this today.
> 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
>Priority: Major
> Fix For: 3.0.1
>
> Attachments: build.log, pom.xml
>
>
> 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 the Maven version.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (MPIR-376) LightweightHttpsWagon is always used
[
https://issues.apache.org/jira/browse/MPIR-376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16771380#comment-16771380
]
Michael Osipov commented on MPIR-376:
-
All ITs pass locally here.
> 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
>Priority: Major
> Attachments: build.log, pom.xml
>
>
> 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 the Maven version.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MPIR-376) LightweightHttpsWagon is always used
[
https://issues.apache.org/jira/browse/MPIR-376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16770677#comment-16770677
]
Robert Scholte commented on MPIR-376:
-
Must be verified with the integration tests. I'm not 100% sure if reducing the
scope to test will effect the runtime. Maybe {{}} is better in this
case.
> 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
>Priority: Major
> Attachments: build.log, pom.xml
>
>
> 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 the Maven version.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MPIR-376) LightweightHttpsWagon is always used
[
https://issues.apache.org/jira/browse/MPIR-376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16770638#comment-16770638
]
Michael Osipov commented on MPIR-376:
-
[~rfscholte], I'd like to know your opinion on that. Is changing this one line
fine?
> 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
>Priority: Major
> Attachments: build.log, pom.xml
>
>
> 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 the Maven version.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MPIR-376) LightweightHttpsWagon is always used
[
https://issues.apache.org/jira/browse/MPIR-376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16770634#comment-16770634
]
Jan Gerken commented on MPIR-376:
-
[~michael-o] I have built MPRI from Git. Removing the dependency on Lightweight
Wagon entirely does not work, it is required by the unit tests. Changing the
scope from `runtime` to `test` makes the tests succeed and solves this issue.
Should I create a PR on GitHub for it?
> 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
>Priority: Major
> Fix For: waiting-for-feedback
>
> Attachments: build.log, pom.xml
>
>
> 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 the Maven version.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MPIR-376) LightweightHttpsWagon is always used
[
https://issues.apache.org/jira/browse/MPIR-376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16770246#comment-16770246
]
Michael Osipov commented on MPIR-376:
-
I see the issue, this is caused by adding the Wagon implementation to the POM.
[~rfscholte], this has been introduced by MPIR-366. Do we really need that
runtime dependency? Maven comes with a HTTP transport by default.
[~jan-apache-issues], can you build MPIR yourself from Git and remove the
dependency on Lightweight Wagon? Does this work for you?
> 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
>Priority: Major
> Attachments: build.log, pom.xml
>
>
> 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 the Maven version.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MPIR-376) LightweightHttpsWagon is always used
[
https://issues.apache.org/jira/browse/MPIR-376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16622595#comment-16622595
]
Jan Gerken commented on MPIR-376:
-
I have added a minimal example. To get the warning, you need Maven >= 3.0.4 and
the following configuration in your {{settings.xml}}:
{code:xml}
central
httpclient
5000
{code}
Additionally, you one of the artefacts must not be present in your local
repository. The easiest solution is to rename your {{~/.m2/repository}} folder.
Now call
{code:java}
mvn site
{code}
I have attached the log of my build.
> 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
>Priority: Major
> Attachments: build.log, pom.xml
>
>
> 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 the Maven version.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MPIR-376) LightweightHttpsWagon is always used
[
https://issues.apache.org/jira/browse/MPIR-376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16615294#comment-16615294
]
Michael Osipov commented on MPIR-376:
-
Please provide a sample project.
> 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
>Priority: Major
>
> 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 the Maven version.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
