No one consistent way to specify a proxy

Description

From an end users perspective, the proxy configuration/handling right now is quite irritating, because neither the default maven proxy settings nor the java-based convention to define http proxies (http://docs.oracle.com/javase/6/docs/technotes/guides/net/proxies.html) are considered.
I don't know the reasons for that development, probably there are good ones. However, I think it would be a great improvement to the cargo maven2 plugin, if there was only one consistent way to specify a proxy (both for ZipInstaller/ArtifactDownloader and remote deployment), which IMHO should be the proxy from the maven settings.

Status

Assignee

Savas Ali Tokmen

Reporter

Robert

Components

Fix versions

Affects versions

1.2.2

Priority

Minor