Mailing-List: contact m2-dev-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Maven 2 Developers List" <m2-dev@maven.apache.org>
Received-SPF: pass (hermes.apache.org: local policy)
Message-ID: <25670558.1110356518077.JavaMail.jira@beaver.codehaus.org>
Date: Wed, 9 Mar 2005 03:21:58 -0500 (EST)
From: "John Casey (JIRA)" <jira@codehaus.org>
To: m2-dev@maven.apache.org
Subject: [jira] Resolved: (MNG-158) implement user configuration
In-Reply-To: <32410377.1109551429608.JavaMail.orion@beaver.codehaus.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

     [ http://jira.codehaus.org/browse/MNG-158?page=history ]
     
John Casey resolved MNG-158:
----------------------------

    Resolution: Fixed

model added; wagon-manager refers to userModel for authentication info via MavenAuthenticationInfoProvider in maven-core; utility class used to read/write and navigate UserModel object.

The userModel is in ~/.m2/user.xml

> implement user configuration
> ----------------------------
>
>          Key: MNG-158
>          URL: http://jira.codehaus.org/browse/MNG-158
>      Project: m2
>         Type: New Feature
>   Components: maven-core
>     Reporter: Brett Porter
>     Assignee: John Casey
>      Fix For: 1.0-alpha-1

>
>
> Currently, we are looking at allowing a user to configure some maven properties specifically for themselves.
> But what about configuration that is tied specifically to a user?
> Specific things:
> - installation locations (JDKs, repository, plugins - some may be set
> > for site)
> - connections (remote servers, type, username, password keys)
> - password cache
> The present thinking is that some of these settings might be set in the USD.
> This can continue, and while this makes sense for general settings and would work as an override, it would be better to centralise this configuration and keep it secure (especially WRT passwords). Maven could prompt a user and update this information (think SSH and known_hosts) - in the USD the precise location to do that may be difficult and would probably default to the user directory.
> Later on, a GUI could be used to configure this, and it could be setup for a user during installation.
> User configuration could be referenced in a POM ${user.foo}, ${maven.repo.local} (rename as user.repository for consistency), etc.
> Some common settings: server, username, password for scm, site target, proxy, repository (basic auth), distribution, issue tracker, wiki, etc.
> Now, many of these may be the same, so there should be a default that is used if another is not given.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira