Closed OliverMatz closed 1 year ago
pending pull request: https://github.com/jfrog/artifactory-maven-plugin/pull/15
@OliverMatz, Thanks for reporting this issue.
Maven Artifactory plugin 3.2.3 is released. This version should include the fix for this issue - feel free to upgrade.
We'd appreciate your feedback on that.
Our maven build runs on a machine that can connect to the internet only via an HTTP-proxy. The target nexus artifactory is only available via the internet. Although the http proxy is correctly configured (1) in the file
.m2/settings.xml
and (2) in the four environment variables[http[s]_(proxy|port)]
and (3) in the four java standard system propertieshttp[s].proxy(Host|Port)
, the artifactory-maven-plugin does not use and the attempt to deploy to the nexus artifactory fails with an exception: {noformat} [ERROR] Internal error: java.lang.RuntimeException: java.util.concurrent.ExecutionException: java.lang.RuntimeException: Error occurred while publishing artifact to Artifactory: ... [ERROR] Skipping deployment of remaining artifacts (if any) and build info. Connect to targethost.de:443 [targethost.de/111.22.33.44] failed: Connection timed out: connect {noformat}I would like to see some documented way to use the http proxy. Preferrably, the artifactory-maven-plugin should use the http proxy configured in the file .m2/settings.xml, but I would be happy with any other reliable way that somehow fits into the configuration framework.
Additional context