maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lukas Theussl (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MPSCM-85) scm:update now no longer uses cached authorisation
Date Mon, 21 Aug 2006 16:28:48 GMT
    [ http://jira.codehaus.org/browse/MPSCM-85?page=comments#action_72921 ] 
            
Lukas Theussl commented on MPSCM-85:
------------------------------------

That should be it. Or use 
maven plugin:download -Dmaven.repo.remote=http://www.ibiblio.org/maven,http://people.apache.org/repo/m1-snapshot-repository/
-DgroupId=maven -DartifactId=maven-scm-plugin -Dversion=1.6.1-SNAPSHOT

> scm:update now no longer uses cached authorisation
> --------------------------------------------------
>
>                 Key: MPSCM-85
>                 URL: http://jira.codehaus.org/browse/MPSCM-85
>             Project: maven-scm-plugin
>          Issue Type: Bug
>    Affects Versions: 1.6
>         Environment: winxp, maven 1.1-beta-3, cvsnt as the cvs client
>            Reporter: dion gillard
>
> In maven 1.1-beta-2, we could use an scm url like this:
> scm:cvs:pserver:dion@cvsserver:/cvs:InterfacesWeb
> and scm:update would happily run.
> With v1.6, we now need to specify a password in the url, e.g.
> scm:cvs:pserver:dion:password@cvsserver:/cvs:InterfacesWeb
> This regression is insecure and forces us to either provide the password in the url,
or set up anonymous read access to the repository (which we do not want to do for security
reasons).
> It also means that the changelog plugin can not be used, as it expects the cvs url to
have 6 tokens:
> BUILD FAILED
> File...... file:/C:/Documents and Settings/db2admin/.maven/cache/maven-changelog-plugin-1.9.1/plugin.jelly
> Element... changelog:changelog
> Line...... 134
> Column.... 15
> cvs repository connection string doesn't contain six tokens
> Total time   : 55 seconds
> Finished at  : Friday, 11 August 2006 11:30:22 AM

-- 
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message