maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Bentmann (JIRA)" <>
Subject [jira] Closed: (MNG-4334) maven core caches settings.xml
Date Wed, 02 Sep 2009 10:19:42 GMT


Benjamin Bentmann closed MNG-4334.

         Assignee: Benjamin Bentmann
       Resolution: Fixed
    Fix Version/s: 3.0-alpha-3

Moved proxies into requests in [r810444|].

> maven core caches settings.xml
> ------------------------------
>                 Key: MNG-4334
>                 URL:
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Embedding
>    Affects Versions: 3.0
>            Reporter: Igor Fedorenko
>            Assignee: Benjamin Bentmann
>             Fix For: 3.0-alpha-3
> From
> {quote}
> m2e does not always use current settings.xml. For example, changes to mirror configuration
are not picked up until m2e restart.
> After initial investigation the problem comes from mirror information cached in DefaultMirrorBuilder.
LegacyRepositorySystem#authentications and LegacyRepositorySystem#proxies will likely cause
similar problem for authentication and proxy configuration respectively.
> Proper solution most will likely require changes to the way maven core handles configuration
from settings.xml. Ideally, everything should be encapsulated in MavenExecutionRequest and
all maven core components should be completely stateless.
> {quote}

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message