jgneff commented on issue #11011: URL: https://github.com/apache/maven/issues/11011#issuecomment-5934854282
Just a follow-up now that Maven 3.10.0 is released: * As expected, using system properties to define the proxies along with the Artifact Resolver 1.x property `aether.connector.http.useSystemProperties=true` no longer works. However, using the new Artifact Resolver 2.x property `aether.transport.apache.useSystemProperties=true` does work. * Using the *settings.xml* file to define the proxies with values interpolated from the system properties as shown above works now, too. Thank you! ๐ The only remaining problems I'm hitting now with Maven 3.10.0 are those mentioned in the issue, [Maven HTTP Proxy support #2519](https://github.com/apache/maven/issues/2519), which I can work around, and a new test case that seems to be ignoring the proxy settings altogether, which forces me to add `-DskipTests=true` to my build of Maven. The Maven tests fail as follows when using a proxy server, no matter how it's defined (either in the *settings.xml* file or using the Artifact Resolver 2.x property): ``` [ERROR] Failures: [ERROR] RepositorySystemSupplierTest.smoke:60 expected: <true> but was: <false> [ERROR] Errors: [ERROR] RepositorySystemSupplierTest.smokeV2Feature:82 ยป DependencyCollection Failed to read artifact descriptor for org.apache.maven:maven-resolver-provider:jar:3.6.1 [ERROR] Tests run: 34, Failures: 1, Errors: 1, Skipped: 0 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:3.6.0:test (default-test) on project maven-resolver-provider: There are test failures. Caused by: java.net.UnknownHostException: repo.maven.apache.org ``` For now, I'm just skipping all tests in the build so that I can [publish Maven 3.10.0](https://snapcraft.io/strictly-maven). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
