You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@continuum.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2008/04/02 13:47:58 UTC
[jira] Updated: (CONTINUUM-659) svn authorisation parameters not
initially extracted from pom.xml
[ http://jira.codehaus.org/browse/CONTINUUM-659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated CONTINUUM-659:
-----------------------------------
Fix Version/s: (was: Future)
1.x
> svn authorisation parameters not initially extracted from pom.xml
> -----------------------------------------------------------------
>
> Key: CONTINUUM-659
> URL: http://jira.codehaus.org/browse/CONTINUUM-659
> 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
> Priority: Minor
> Fix For: 1.x
>
>
> 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: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira