jira-importer commented on issue #1075: URL: https://github.com/apache/maven-scm/issues/1075#issuecomment-2964644206
**[Konrad Windszus](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=kwin)** commented I have the same issue and seems indeed occur in case when the released artifact is not in the root of the repository (similar to SCM-740). I fail to see how a fix being applied for SCM-740 could be easily transferred to https://github.com/apache/maven-scm/blob/master/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-jgit/src/main/java/org/apache/maven/scm/provider/git/jgit/command/status/JGitStatusCommand.java. [Mark Struberg](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=struberg) Since you came up with the original fix for SCM-740, could you have a look what needs to be changed in the JGit provider to support that use case as well? Also it would probably be good to extend the TCK to cover this use case, to check that all providers support that properly. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
