You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jan Lisse (JIRA)" <ji...@codehaus.org> on 2007/08/03 14:22:13 UTC
[jira] Created: (CONTINUUM-1360) Prepended semicolon in svn
password does not work
Prepended semicolon in svn password does not work
-------------------------------------------------
Key: CONTINUUM-1360
URL: http://jira.codehaus.org/browse/CONTINUUM-1360
Project: Continuum
Issue Type: Bug
Components: Web interface
Affects Versions: 1.1-beta-1
Environment: Suse Linux 10.2, 64-Bit, Java 1.6
Reporter: Jan Lisse
If i have a prepended semicolon in my scm (Subversion) password, for example ";password" Continuum generates a faulty commandline for svn checkout.
Before i used 1.1-alpha-2 with success. So i guess the handling of form input data has changed in 1.1-beta-1.
I had no time to do further tests, but i guess there are problems with other special chars too.
--
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
[jira] Commented: (CONTINUUM-1360) Prepended semicolon in svn
password does not work
Posted by "Jan Lisse (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-1360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_104309 ]
Jan Lisse commented on CONTINUUM-1360:
--------------------------------------
Today i had some time digging into the sources and i figured out that the problem is not Continuum related but caused
by a bug in the maven-scm-provider-svnexe. It does not properly quote passwords used on the commandline.
I created a JIRA issue for it here: http://jira.codehaus.org/browse/SCM-334 and attached a patch to fix it.
Continuum should upgrade to a new mvn-scm-provider-svnexe version as soon as a new release with the fix is available.
> Prepended semicolon in svn password does not work
> -------------------------------------------------
>
> Key: CONTINUUM-1360
> URL: http://jira.codehaus.org/browse/CONTINUUM-1360
> Project: Continuum
> Issue Type: Bug
> Components: Web interface
> Affects Versions: 1.1-beta-1
> Environment: Suse Linux 10.2, 64-Bit, Java 1.6
> Reporter: Jan Lisse
>
> If i have a prepended semicolon in my scm (Subversion) password, for example ";password" Continuum generates a faulty commandline for svn checkout.
> Before i used 1.1-alpha-2 with success. So i guess the handling of form input data has changed in 1.1-beta-1.
> I had no time to do further tests, but i guess there are problems with other special chars too.
--
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
[jira] Commented: (CONTINUUM-1360) Prepended semicolon in svn
password does not work
Posted by "Jan Lisse (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-1360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103922 ]
Jan Lisse commented on CONTINUUM-1360:
--------------------------------------
A little addition: The initial download of the pom.xml of my Maven2 project works fine using the same credentials.
But when triggering a build the checkout fails with a faulty commandline. Svn complains about missing argument --password.
> Prepended semicolon in svn password does not work
> -------------------------------------------------
>
> Key: CONTINUUM-1360
> URL: http://jira.codehaus.org/browse/CONTINUUM-1360
> Project: Continuum
> Issue Type: Bug
> Components: Web interface
> Affects Versions: 1.1-beta-1
> Environment: Suse Linux 10.2, 64-Bit, Java 1.6
> Reporter: Jan Lisse
>
> If i have a prepended semicolon in my scm (Subversion) password, for example ";password" Continuum generates a faulty commandline for svn checkout.
> Before i used 1.1-alpha-2 with success. So i guess the handling of form input data has changed in 1.1-beta-1.
> I had no time to do further tests, but i guess there are problems with other special chars too.
--
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