goutamadwant opened a new pull request, #2148:
URL: https://github.com/apache/maven-resolver/pull/2148

   Related to #2139.
   
   With `aether.connector.http.useSystemProperties=true`, the Apache transport 
uses the configured proxy but ignores its username and password, causing HTTP 
407. Use matching HTTP or HTTPS system proxy credentials when explicit Resolver 
authentication is unavailable.
   
   Keep fallback credentials scoped to the actual proxy, separate from 
repository authentication. Clear their authentication state when a redirect 
changes proxy or becomes direct. The opt-in remains disabled by default; this 
adds no public API or runtime dependency.
   
   Tests cover GET/HEAD/PUT, HTTPS CONNECT, explicit credential precedence, 
missing or mismatched properties, origin isolation, and redirects. The native 
regression fails with HTTP 407 on unchanged master.
   
   Validation on Java 21 with Maven 3.9.16:
   
   - `mvn verify`: all 31 modules passed; 2,082 tests, zero failures/errors, 87 
existing skips.
   - `mvn -Prun-its verify`: passed, including 107 integration tests and one 
Invoker build.
   - All 19 new proxy cases ran without skips.
   
   This targets Resolver 2.x. The corresponding 1.9.x backport covers the 
lineage used by Maven 3.9.16.
   
   - [x] The pull request addresses one issue without unrelated changes.
   - [x] The description explains what changed, how, and why.
   - [x] The commit has a meaningful subject and body.
   - [x] Regression tests fail without the runtime fix.
   - [x] `mvn verify` passed.
   - [x] `mvn -Prun-its verify` passed.
   - [ ] I hereby declare this contribution to be licenced under the [Apache 
License Version 2.0, January 2004](https://www.apache.org/licenses/LICENSE-2.0).
   - [ ] File an [Apache Individual Contributor License 
Agreement](https://www.apache.org/licenses/icla.pdf), as applicable.


-- 
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]

Reply via email to