[
https://issues.apache.org/jira/browse/MRESOLVER-327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17697345#comment-17697345
]
Tamas Cservenak commented on MRESOLVER-327:
-------------------------------------------
If you look into transport-http sources (for example here
[https://github.com/apache/maven-resolver/blob/master/maven-resolver-transport-http/src/main/java/org/eclipse/aether/transport/http/GlobalState.java#L154|https://github.com/apache/maven-resolver/blob/master/maven-resolver-transport-http/src/main/java/org/eclipse/aether/transport/http/GlobalState.java#L154)])
you can see transport-http tries to "hold in hands" almost every aspect of
HttpClient. If we'd use this "use system properties" stuff, I have no idea of
following things:
* would something clash in httpclient regardin resolver explicit set things
with some "automated" one
* what happens if settings.xml contains proxy but system property is present
as well
* if both present, which one "wins"?
* etc
> Make tranport-http obey system properties regarding proxy settings
> ------------------------------------------------------------------
>
> Key: MRESOLVER-327
> URL: https://issues.apache.org/jira/browse/MRESOLVER-327
> Project: Maven Resolver
> Issue Type: Improvement
> Components: Resolver
> Reporter: Tamas Cservenak
> Priority: Major
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
