[ http://jira.codehaus.org/browse/CONTINUUM-318?page=all ] Emmanuel Venisse closed CONTINUUM-318: --------------------------------------
Resolution: Fixed Fix Version: (was: 1.0-beta-2) 1.0-beta-1 I updated db schema for all possible long string > 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 > Assignee: Emmanuel Venisse > Priority: Blocker > Fix For: 1.0-beta-1 > Attachments: wrapper.log > > Original Estimate: 30 minutes > Remaining: 30 minutes > > 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