[
https://issues.apache.org/jira/browse/SCM-921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17963664#comment-17963664
]
ASF GitHub Bot commented on SCM-921:
------------------------------------
jira-importer opened a new issue, #1149:
URL: https://github.com/apache/maven-scm/issues/1149
**[Alex
Harui](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=aharui)**
opened
**[SCM-921](https://issues.apache.org/jira/browse/SCM-921?redirect=false)** and
commented
Running Maven release plugin with jgit on Windows Server, the pom.xml files
in subfolders would not get committed. The main pom.xml file would. Upon
investigation it appears that Maven passed in absolute paths to the subfolders
starting with C:\ and JGIT's relativize only works correctly for c:\ (note
capitalization difference). So I patched maven-scm-provider-jgit to lowercase
the first letter of an absolute path if it detects the path has ":\" at index 1
and it appears to be working now.
---
**Affects:** 1.11.1
**Attachments:**
-
[SCM-921.patch](https://issues.apache.org/jira/secure/attachment/12959338/SCM-921.patch)
(_1.38 kB_)
> maven-scm-provider-jgit not handling relative paths on Windows Server
> ---------------------------------------------------------------------
>
> Key: SCM-921
> URL: https://issues.apache.org/jira/browse/SCM-921
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Components: maven-scm-provider-jgit
> Affects Versions: 1.11.1
> Reporter: Alex Harui
> Priority: Major
> Attachments: SCM-921.patch
>
>
> Running Maven release plugin with jgit on Windows Server, the pom.xml files
> in subfolders would not get committed. The main pom.xml file would. Upon
> investigation it appears that Maven passed in absolute paths to the
> subfolders starting with C:\ and JGIT's relativize only works correctly for
> c:\ (note capitalization difference). So I patched maven-scm-provider-jgit
> to lowercase the first letter of an absolute path if it detects the path has
> ":\" at index 1 and it appears to be working now.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
