[
https://issues.apache.org/jira/browse/SCM-746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17962863#comment-17962863
]
ASF GitHub Bot commented on SCM-746:
------------------------------------
jira-importer commented on issue #955:
URL: https://github.com/apache/maven-scm/issues/955#issuecomment-2964635895
**[Michael
Osipov](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=michael-o)**
commented
Please share the entire Maven output as well as the command you have issued.
> Use '--' to separate filenames from revisions within Git
> --------------------------------------------------------
>
> Key: SCM-746
> URL: https://issues.apache.org/jira/browse/SCM-746
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Components: maven-scm-provider-gitexe
> Affects Versions: 1.9
> Environment: git version 1.7.10.5
> Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19
> 13:51:28+0000)
> Java version: 1.7.0_45, vendor: Oracle Corporation
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "2.6.32-358.11.1.el6.x86_64", arch: "amd64",
> family: "unix"
> Reporter: deckrider
> Priority: Minor
>
> We had a maven multi module project where a module was unfortunately named
> "master".
> This caused a problem when working on the Git master branch:
> Provider message: The git-log command failed. Command output:
> -------------------------------------------------------------------------------
> From file:///foo/bar * branch master -> FETCH_HEAD
> fatal: ambiguous argument 'master': both revision and filename Use '--' to
> separate filenames from revisions
> -------------------------------------------------------------------------------
> Our workaround was to rename the "master" module to "master-module" and
> reflect that in the parent pom which lists all the module directories.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
