maven-m2-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From j...@codehaus.org
Subject [jira] Work Started: (MNG-158) implement user configuration
Date Mon, 28 Feb 2005 00:45:45 GMT
Message:

   Work on this issue has been started by Brett Porter (mailto:brett@codehaus.org)

---------------------------------------------------------------------
View the issue:
  http://jira.codehaus.org/browse/MNG-158

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MNG-158
    Summary: implement user configuration
       Type: New Feature

     Status: In Progress
   Priority: Major

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: m2
 Components: 
             maven-core
   Fix Fors:
             1.0-alpha-1

   Assignee: Brett Porter
   Reporter: Brett Porter

    Created: Sun, 27 Feb 2005 7:42 PM
    Updated: Sun, 27 Feb 2005 7:43 PM

Description:
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.



---------------------------------------------------------------------
JIRA INFORMATION:
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


Mime
View raw message