[
https://issues.apache.org/jira/browse/SCM-732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17962770#comment-17962770
]
ASF GitHub Bot commented on SCM-732:
------------------------------------
jira-importer commented on issue #937:
URL: https://github.com/apache/maven-scm/issues/937#issuecomment-2964634217
**[Jan
Ruzicka](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=jan.ruzicka)**
commented
What would be a right way to separate interaction with older and newer
command line client?
Did any other providers solve similar issue?
> plugin desn't work with command line client past 2009R2
> -------------------------------------------------------
>
> Key: SCM-732
> URL: https://issues.apache.org/jira/browse/SCM-732
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Components: maven-scm-provider-starteam
> Affects Versions: 1.8.1
> Environment: StarTeam 12.0 and higher
> Reporter: Jan Ruzicka
> Priority: Major
>
> The command line client (stcmd) options and parameters changed in StarTeam
> 12.0 (cca. October 2011).
> The new version of stcmd does not accept options previously accepted and
> quits with error.
> Main problem is option "nologo" as plugin passes it to all invocations of
> stcmd.
> Some sub-commands were also remove or replaced such as "history", which was
> replaced by "select" with a query parameter specifying history.
> Further StarTeam documentation is available at microfocus site[1].
> [1] http://supportline.microfocus.com/productdoc.aspx
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
