maven-m2-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Maczka Michal <michal.mac...@imtf.ch>
Subject RE: cvs commit: maven-components/maven-model maven.mdo
Date Thu, 03 Feb 2005 12:05:17 GMT


> -----Original Message-----
> From: brett@apache.org [mailto:brett@apache.org]
> Sent: Thursday, February 03, 2005 12:39 PM
> To: maven-components-cvs@apache.org
> Subject: cvs commit: maven-components/maven-model maven.mdo
> 

[...]
>   Log:
>   o add basic auth to model and lightweight wagon
>   +        <field>
>   +          <name>username</name>
>   +          <version>4.0.0</version>
>   +          <description>The username to connect to the 
> repository with. If omitted, none is used.</description>
>   +          <type>String</type>
>   +        </field>
>   +        <!-- @todo this should be encrypted in some way or 
> be a keystore lookup and m2 can provide a way to generate it -->
>   +        <field>
>   +          <name>password</name>
>   +          <version>4.0.0</version>
>   +          <description>The password to use when connecting 
> to the repository. If omitted, none is used.</description>
>   +          <type>String</type>
>   +        </field>
>          </fields>
>          <codeSegments>
>            <codeSegment>
>   
>   
>   
IMO credentials are definitly not a part of the model.
Simply they are different for each user. The same applies to proxy server
settings.


What about re-implementing this functinality in the way it was done in early
days of m2?
I mean to have them in some configuration files 
(e.g. {user.home}/m2/proxy.xml   and ${user.home}/m2/auth.xml).?

With plexus config linking capabilities should be super simple thing to do.

( I mean  things like:

<file-configuration-resource source="${user.home}/m2/auth.xml"/>
or
<directory-configuration-resource source="${user.home}/m2/auths/"
includes="*.xml"/>
)

Michal

Mime
View raw message