I thought maven-scm-plugin already bound to maven, would it make sense to talk to
maven to pickup user's private info?
I think this pattern is usable future mojo that may need remote authentication.
and the capility to store user info in one place (settings.xml) is important.
-D
On 10/25/05, Jason van Zyl <[EMAIL PROTECTED]> wrote:
On Fri, 2005-10-21 at 16:48 -0500, Dan Tran (JIRA) wrote:
> ability to store user password in settings.xml
> ----------------------------------------------
>
> Key: SCM-64
> URL: http://jira.codehaus.org/browse/SCM-64
> Project: Maven SCM
> Type: Bug
> Components: maven-plugin
> Versions: 1.0-alpha-4
> Environment: xp
> Reporter: Dan Tran
> Fix For: 1.0-alpha-4
>
>
> It think we should manage user/password via settings.xml and command line can overide them.
Maven SCM, as a tool, should not need to now anything about Maven
specifically. The bridge should be created in Maven in order to pull
user specific information and feed it into Maven SCM.
>
>
--
jvz.
Jason van Zyl
jason at maven.org
http://maven.apache.org
People develop abstractions by generalizing from concrete examples.
Every attempt to determine the correct abstraction on paper without
actually developing a running system is doomed to failure. No one
is that smart. A framework is a resuable design, so you develop it by
looking at the things it is supposed to be a design of. The more examples
you look at, the more general your framework will be.
-- Ralph Johnson & Don Roberts, Patterns for Evolving Frameworks
