[
https://issues.apache.org/jira/browse/SCM-791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17963116#comment-17963116
]
ASF GitHub Bot commented on SCM-791:
------------------------------------
jira-importer commented on issue #1019:
URL: https://github.com/apache/maven-scm/issues/1019#issuecomment-2964639354
**[Ilya
Basin](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=basinilya)**
commented
[Michael
Osipov](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=michael-o)
It helps to modify GitChangeLogCommand like this: cl.createArg().setValue(
"." );
We do "cd workdir" to run shell commands on Linux, don't we?
The expected values in GitChangeLogCommandTest should be updated accordingly.
I see you have removed getAbsolutePath from GitScmTestUtils.getScmUrl.
That's not right. Users should be able to do something like this:
"scm:git:file://${basedir}" and "${basedir}" may be like "C:\something" or
"\\unc\path". This is why I replace the slashes so late in
GitScmProviderRepository.
> GitExe Provider does not work properly in Cygwin
> ------------------------------------------------
>
> Key: SCM-791
> URL: https://issues.apache.org/jira/browse/SCM-791
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Components: maven-scm-provider-gitexe
> Affects Versions: 1.9.2
> Environment: Cygwin under Windows 8
> Reporter: Irineu Ruiz
> Assignee: Michael Osipov
> Priority: Critical
> Fix For: 1.11.1
>
> Attachments: bad-01ba0c0.txt, good-SCM-791.txt,
> test_1.9.2_Cygwin.log, test_1.9.2_prompt.log, test_HEAD_Cygwin.log,
> test_HEAD_prompt.log
>
>
> The tests of the maven-scm project fails in CygWin and passed in command
> prompt, as you can see in the attachment.
> Also, using Cygwin under Windows 8, we can't execute a mvn release:prepare
> properly, because pom.xml is not correct commited in tag and HEAD of
> repository.
> The maven gives a false positive of Build Sucess, but the tag is incorret,
> with the SNAPSHOT termination in version.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
