continuum-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brett Porter (JIRA)" <>
Subject [jira] Closed: (CONTINUUM-659) svn authorisation parameters not initially extracted from pom.xml
Date Wed, 22 Apr 2009 16:12:45 GMT


Brett Porter closed CONTINUUM-659.

      Assignee: Brett Porter
    Resolution: Won't Fix

you can enter it into the form now. Putting it in the POM is a bad idea.

> svn authorisation parameters not initially extracted from pom.xml
> -----------------------------------------------------------------
>                 Key: CONTINUUM-659
>                 URL:
>             Project: Continuum
>          Issue Type: Bug
>          Components: SCM
>    Affects Versions: 1.0.3
>         Environment: Suse Linux 9.1; Sun j2sdk1.4.2_11, subversion 1.3.1
>            Reporter: Stephen Coy
>            Assignee: Brett Porter
>            Priority: Minor
> When a pom.xml is initially added on the ../addMavenTwoProject page, the scm info from
it is decomposed at some point so that the project can be checked out of subversion.
> However, continuum does not seem to gather the username/password from the scm url and
it fails to authorise itself properly with subversion.
> If you then choose to edit the project scm details in the web interface, the username/password
has been extracted and subversion checkouts will subsequently be properly authorised after
simply submitting the project details with no changes.
> The connection url I have been using is similar to:
>     <connection>scm:svn:http://myuserid:mypassword@cvs.axegroup.local/svn/my/module/trunk</connection>

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message