You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (Jira)" <ji...@apache.org> on 2022/05/31 14:54:00 UTC

[jira] [Commented] (SCM-990) Jgit Provider cannot resolve Repository in multi-module Maven Project

    [ https://issues.apache.org/jira/browse/SCM-990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17544441#comment-17544441 ] 

Michael Osipov commented on SCM-990:
------------------------------------

That is not a bug. You must invoke from the parent and use {{-pl}}.

> 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
>          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.7#820007)