[
https://issues.apache.org/jira/browse/SCM-990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17965148#comment-17965148
]
Olivier Lamy commented on SCM-990:
----------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-scm#1217|https://github.com/apache/maven-scm/issues/1217].
> Jgit Provider cannot resolve Repository in multi-module Maven Project
> ---------------------------------------------------------------------
>
> Key: SCM-990
> URL: https://issues.apache.org/jira/browse/SCM-990
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Components: maven-scm-provider-jgit
> Reporter: Enrico Horn
> Priority: Major
>
> The JGit providers info command (and probably others) uses fielset.basedir as
> git working directory. When running maven command in a submodule this will
> result in the following error:
>
> Cannot get the revision information from the scm repository :
> [ERROR] Exception while executing SCM command. JGit resolve failure!
> repository not found: <submodule folder>
>
> What it should do instead is act like the git binary and search for the git
> directory in parent directories if none found in the current one. Jgit has
> the API FileRepositoryBuilder.findGitDir to do that.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
