[ http://jira.codehaus.org/browse/CONTINUUM-318?page=comments#action_47136 
] 

Emmanuel Venisse commented on CONTINUUM-318:
--------------------------------------------

The error isn't caused by your long scm connection string but the scm provider 
message length.
I'll fix the length of it.

I've seen that you got an authentication failure on svn:
INFO   | jvm 1    | 2005/09/25 15:20:27 | 2005-09-25 15:20:27,929 [Thread-0] 
WARN  ContinuumScm                   - Command output: svn: PROPFIND request 
failed on 
'/repos/proxiad/Socle/Passage%20%c3%a0%20Maven%202%20et%20WTP/Tentative%20de%20projets%20Maven%202%20sous%20Eclipse%20WTP%200.7/my-app'
INFO   | jvm 1    | 2005/09/25 15:20:27 | svn: PROPFIND of 
'/repos/proxiad/Socle/Passage%20%c3%a0%20Maven%202%20et%20WTP/Tentative%20de%20projets%20Maven%202%20sous%20Eclipse%20WTP%200.7/my-app':
 authorization failed (https://turenne.vidal.biz)
INFO   | jvm 1    | 2005/09/25 15:20:27 | 


> Maven 2 build fails with a derby jdbc truncation error on a long scm 
> connection string
> --------------------------------------------------------------------------------------
>
>          Key: CONTINUUM-318
>          URL: http://jira.codehaus.org/browse/CONTINUUM-318
>      Project: Continuum
>         Type: Bug
>     Versions: 1.0-alpha-4
>     Reporter: Cédric Vidal
>     Priority: Blocker
>      Fix For: 1.0-beta-1
>  Attachments: wrapper.log
>
>
> It might be caused by a quite long subversion scm connection string:
> scm:svn:https://[EMAIL 
> PROTECTED]/repos/proxiad/Socle/Passage%20%c3%a0%20Maven%202%20et%20WTP/Tentative%20de%20projets%20Maven%202%20sous%20Eclipse%20WTP%200.7
> I have attached the full wrapper.log for the following scenario: start 
> continuum, trigger build manually, stop continuum.
> The pom's scm configuration is as follows:
> <scm>
> <connection>scm:svn:https://[EMAIL 
> PROTECTED]/repos/proxiad/Socle/Passage%20%c3%a0%20Maven%202%20et%20WTP/Tentative%20de%20projets%20Maven%202%20sous%20Eclipse%20WTP%200.7</connection>
> </scm>

-- 
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

Reply via email to