[ https://issues.apache.org/jira/browse/MRESOLVER-382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tamas Cservenak updated MRESOLVER-382: -------------------------------------- Fix Version/s: 1.9.14 (was: 1.10.0) > Define local outgoing (bind) address > ------------------------------------ > > Key: MRESOLVER-382 > URL: https://issues.apache.org/jira/browse/MRESOLVER-382 > Project: Maven Resolver > Issue Type: Improvement > Components: Resolver > Reporter: Benjamin Marwell > Assignee: Tamas Cservenak > Priority: Major > Fix For: 1.9.14 > > > Currently, outgoing PUT connections (or download from central for that > matter) will be resolved over the default route. > However, this is not always feasible. > h2. Expected behaviour > A new property {{aether.connector.http.bind.address}} is defined for outgoing > requests, so that other routes (other interfaces) can be used. > h2. Actual behaviour > Certain systems cannot be reached when a firewall is only opened on a > non-default interface. > h2. User Story > Builds on servers with multiple interfaces: > * The default route is defined poorly > * Other interfaces are available and have the requested firewall rules > * User defines -Daether.connector.http.bind.address=${myotherip} (or local > address) to make outgoing connections to bind to another interface than the > default one. -- This message was sent by Atlassian Jira (v8.20.10#820010)