[
https://issues.apache.org/jira/browse/SCM-791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16577964#comment-16577964
]
Ilya Basin edited comment on SCM-791 at 8/13/18 9:18 AM:
---------------------------------------------------------
[~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.
was (Author: basinilya):
[~michael-o]
It helps to modify GitChangeLogCommand like this: cl.createArg().setValue( "."
);
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.
> maven-scm-provider-gitexe - Lastest version (1.9.2) doesn't work properly in
> Cygwin
> -----------------------------------------------------------------------------------
>
> Key: SCM-791
> URL: https://issues.apache.org/jira/browse/SCM-791
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-gitexe
> Affects Versions: 1.9.2
> Environment: Cygwin under Windows 8
> Reporter: Irineu Ruiz
> Priority: Critical
> Fix For: waiting-for-feedback
>
> 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
(v7.6.3#76005)
