[
https://issues.apache.org/jira/browse/SCM-202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17960605#comment-17960605
]
ASF GitHub Bot commented on SCM-202:
------------------------------------
jira-importer commented on issue #433:
URL: https://github.com/apache/maven-scm/issues/433#issuecomment-2964594233
**[Thorsten H.
Riek](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=thr)**
commented
Here is the patch to fix the test. I also moved the vss-settings loader to
VssCommandLineUtils.java for better reusability.
> changelog.VssHistoryCommandTest testCommandLine fails if VSS plugin is
> configured
> ---------------------------------------------------------------------------------
>
> Key: SCM-202
> URL: https://issues.apache.org/jira/browse/SCM-202
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Components: maven-scm-provider-vss
> Affects Versions: 1.0-beta-4
> Reporter: Thorsten H. Riek
> Assignee: Emmanuel Venisse
> Priority: Major
> Fix For: 1.0-beta-4
>
> Attachments: SCM-202-maven-scm-provider-vss.patch,
> TEST-org.apache.maven.scm.provider.vss.VssScmProviderTest.xml,
> TEST-org.apache.maven.scm.provider.vss.commands.changelog.VssHistoryCommandTest.xml,
> vss-settings.xml
>
>
> If there is a vss-settings.xml is provided the testcase faild.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
