gnodet commented on issue #7847:
URL: https://github.com/apache/maven/issues/7847#issuecomment-4110310848

   This issue (MNG-5984) was fixed in Maven 3.6.x (commit `5a4d548103`, Feb 
2016) by updating core extension resolution to include repositories from active 
settings.xml profiles.
   
   In Maven 4, this is even more robustly handled through the session-based 
architecture. The `Session` object carries all repository configuration — 
including repositories from `activeByDefault` profiles in settings.xml — and 
this configuration is propagated consistently through all artifact resolution 
paths, including core extension resolution.
   
   Maven 4's `DefaultModelBuilder` explicitly passes 
`request.getSession().getRemoteRepositories()` (which includes settings profile 
repositories) to all derived model builder requests, ensuring no resolution 
path is missing profile-defined repositories.
   
   _Claude Code on behalf of Guillaume Nodet_


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