[ https://jira.codehaus.org/browse/SCM-634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte updated SCM-634: ------------------------------- Attachment: SCM-634-test.patch Issue confirmed (see attached test). The problem is caused by tokening the third part of the connection. Here the code has no idea what the original delimeter was. So it tries both {{|}} and {{:}}. A workaround might be to add a pipe to the URL {code:xml} <developerConnection>scm|clearcase|c:\views\tempview\configSpec.txt|</developerConnection> {code} > Clearcase provider status keeps displaying "Can't load the scm provider. You > need to define a connectionUrl parameter" but connection node is defined. > ------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: SCM-634 > URL: https://jira.codehaus.org/browse/SCM-634 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-clearcase > Affects Versions: 1.5 > Environment: Windows > Reporter: Justin Bleach > Attachments: SCM-634-test.patch > > > POM has been defined correctly: > <project> > ...... > <scm> > > <connection>scm|clearcase|c:\views\tempview\configSpec.txt</connection> > > <developerConnection>scm|clearcase|c:\views\tempview\configSpec.txt</developerConnection> > </scm> > ...... > </project> > Plugin configuration points to "connection". When doing a 'mvn scm:status' > keeps telling me "Can't load the scm provider. You need to define a > connectionUrl parameter". However I am pointing to a valid configSpec('mvn > scm:validate' = success) and connection is defined as shown above. > ConfigSpec (for completeness) is: > element * CHECKEDOUT > element -dir * /main/LATEST > element * /main/release_1.0/tempview/LATEST > element * /main/release_1.0/LATEST -mkbranch ac42144_r1.0_t0001 > element * /main/R1.0 -mkbranch release_1.0 > element * /main/{created_since(today)} -mkbranch release_1.0 > load c:\views\tempview\WCSF\CustomerService > Cannot do anything with plugin currently because message prevents code from > being checked out. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira