[
https://issues.apache.org/jira/browse/SCM-750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17964899#comment-17964899
]
Olivier Lamy commented on SCM-750:
----------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-scm#960|https://github.com/apache/maven-scm/issues/960].
> TFS-plugin fails in cases of 'TFS policies' is required by TFS upon checkin
> ---------------------------------------------------------------------------
>
> Key: SCM-750
> URL: https://issues.apache.org/jira/browse/SCM-750
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Components: maven-scm-provider-tfs
> Affects Versions: 1.9
> Environment: TFS-2010
> Reporter: Ohad R
> Assignee: Hervé Boutemy
> Priority: Major
> Fix For: 1.9.1
>
>
> In TFS, there is an option of "checkin policies". In this case, whenever a
> developer checks-in his code, another dialog pops-up , and asks to enter a
> comment. I really do not know who really uses this feature and actually
> enters a real comment (since the comment that is related to the check-in was
> entered in a previous dialog), but in my case the organization's SCM forces
> this extra-dialog.
> *The problem*: when I try to check in a file using a command line, I HAVE TO
> add an extra argument to the command (see example below). Hence, the scm-tfs
> plugin does not work, since it lacks this 'extra' argument. As far as i saw
> the code, I understand that the command is hard-coded, and unfortunately it
> is not configurable,
> *example* command-line for check-in with checkin-policies (only a single
> pom.xml):
> tf checkin -noprompt "-comment:[maven-release-plugin] prepare release
> some-comment-for-checkin" D:\.....\pom.xml /override:";Auto-Build: Version
> Update";
> in this example, '/override:";Auto-Build: Version Update";' is the
> extra-argument.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
