[
https://issues.apache.org/jira/browse/SCM-791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17963110#comment-17963110
]
ASF GitHub Bot commented on SCM-791:
------------------------------------
jira-importer commented on issue #1019:
URL: https://github.com/apache/maven-scm/issues/1019#issuecomment-2964639353
**[Michael
Osipov](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=michael-o)**
commented
Alright, added the Git config and can reproduce now. I have found several
other bugs where a `File` is passed for a URL. I've fixed those too.
Please check my branch `path-fiddle`. Currently, `GitExeChangeLogTckTest`
fails because `GitChangeLogCommand` does this: `cl.createArg().setFile(
workingDirectory )`. This change is valid, but has to be relative to the repo
root to work properly with Cygwin. Also testcases need to be changed.
> 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)
