You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Ohad R (JIRA)" <ji...@codehaus.org> on 2014/06/23 16:15:10 UTC

[jira] (SCM-759) cannot create Branch with TFS-provider: "TF10125: The path must start with $/"

     [ https://jira.codehaus.org/browse/SCM-759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ohad R updated SCM-759:
-----------------------

    Summary: cannot create Branch with TFS-provider: "TF10125: The path must start with $/"  (was: cannot create Branch with TFS-provider: “TF10125: The path must start with $/”)

> cannot create Branch with TFS-provider: "TF10125: The path must start with $/"
> ------------------------------------------------------------------------------
>
>                 Key: SCM-759
>                 URL: https://jira.codehaus.org/browse/SCM-759
>             Project: Maven SCM
>          Issue Type: Bug
>          Components: maven-scm-provider-tfs
>    Affects Versions: 1.9
>         Environment: TFS-2010, SP1
>            Reporter: Ohad R
>
> Running the maven command:
> mvn release:branch -DbranchName=$/NNG/ORK/maven-branch-10
> invokes finally
> tf branch D:\Dev\projects\NNG\ORK\dev\PLS -checkin $/NNG/ORK/maven-branch-10
> this causes an error:
> {color:red}"TF10125: The path must start with $/" {color}
> After a research I found the *checkin* statement causes this problem, because if I comment out the "checkin" argument (in {{org.apache.maven.scm.provider.tfs.command.TfsBranchCommand}}), it works fine. However, we _do_ want to use the "checkin" statement because we want the new branch to be checked-in. I found out that it will be OK to use "checkin", only if we use a TFS path (starts with '$/'), instead of local-path.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)