You are viewing a plain text version of this content. The canonical link for it is here.
Posted to m2-dev@maven.apache.org by ji...@codehaus.org on 2005/02/28 01:43:49 UTC
[jira] Created: (MNG-158) implement user configuration
Message:
A new issue has been created in JIRA.
---------------------------------------------------------------------
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: Open
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:42 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
[jira] Assigned: (MNG-158) implement user configuration
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-158?page=history ]
Brett Porter reassigned MNG-158:
--------------------------------
Assign To: John Casey (was: Brett Porter)
John is doing this
> 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
[jira] Commented: (MNG-158) implement user configuration
Posted by ji...@codehaus.org.
The following comment has been added to this issue:
Author: Brett Porter
Created: Tue, 1 Mar 2005 12:41 AM
Body:
for now, will just use properties. in ~/.m2/maven.properties.
Alternative mdo might parse something like:
<maven>
<java>
<jdks>
<jdk>
<version>1.4.2_06</version>
<home>c:\jdk1.4.2_06</home>
</jdk>
</jdks>
</java>
<servers>
<!-- Note here: we might need finer grained control than host (use an ID? in case you need to log in under different accounts with different permissions, or use one for SSH, one for HTTP -->
<server>
<host>cvs.apache.org</host>
<username>brett</username>
<privateKey>c:\home\brett\.ssh\id_dsa_apache</privateKey>
</server>
</servers>
<profiles>
<profile>
<id>user-2.0-alpha-1</id>
<home>c:\usr\local\maven-2.0-alpha-1</home>
<localRepository>c:\home\brett\.m2\repository</localRepository>
<passwordStore>c:\home\brett\.m2\passwords</passwordStore>
</profile>
<profile>
<id>development</id>
<home>c:\usr\local\maven-2.0-SNAPSHOT</home>
<localRepository>c:\home\brett\.m2\repository</localRepository>
<passwordStore>c:\home\brett\.m2\passwords</passwordStore>
</profile>
</profiles>
<defaults>
<username>bporter</username>
<privateKey>c:\home\brett\.ssh\id_dsa</privateKey>
<profile>user-2.0-alpha-1</profile>
</defaults>
</maven>
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/MNG-158?page=comments#action_30385
---------------------------------------------------------------------
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: Tue, 1 Mar 2005 12:41 AM
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
[jira] Resolved: (MNG-158) implement user configuration
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Work Started: (MNG-158) implement user configuration
Posted by ji...@codehaus.org.
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
[jira] Work stopped: (MNG-158) implement user configuration
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-158?page=history ]
Work on MNG-158 stopped by John Casey
> 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
[jira] Commented: (MNG-158) implement user configuration
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-158?page=comments#action_30577 ]
John Casey commented on MNG-158:
--------------------------------
Added UserModel .mdo and utility to read, and added UserModel to MavenExecutionRequest and MavenSession. Next is to push UserModel support through the DefaultModelBuilder to RepositoryUtils, where it can be used to manage identities for artifact deployment.
> 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
[jira] Work started: (MNG-158) implement user configuration
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-158?page=history ]
Work on MNG-158 started by John Casey
> 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