You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Enrico Horn (Jira)" <ji...@apache.org> on 2022/06/01 09:22: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=17544781#comment-17544781 ] 

Enrico Horn commented on SCM-990:
---------------------------------

I tried -pl and it actually also doesnt work. The base path is still the submodule.

 

FileRepositoryBuilder.findGitDir is the suggestion I already made in the bug report.

> 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)