Some further research on my part shows that a simple connection test
using HttpComponents httpclient 4.3.5 does work, but that the version
of httpclient used in Wagon 2.6 (httpclient 4.3.1) fails. Apparently
the newer version of httpclient fixes the problem I ran into, although
I do not know what
Hi,
may be i miss a thing but wagon can be configured outside of maven via
extensions ...
project
...
build
extensions
extension
groupIdorg.apache.maven.wagon/groupId
artifactIdwagon/artifactId
version2.7/version
/extension
/extensions
Hello Karl,
Are you sure it is possible to override the Wagon version used by
Maven internally? (As opposed to the Wagon provider configured to
deploy artefacts.)
It does not seem to work for me. Artefact wagon won't resolve, and
when I use wagon-http it does not change the behaviour of Maven;
Hello,
I am trying to get Maven (3.2.2) to work with an instance of Archiva
hosted behind a webserver secured with client-side SSL certificates.
I have followed the guide at
https://maven.apache.org/guides/mini/guide-repository-ssl.html, and
imported the server-side SSL certificate into a Java
