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

ASF GitHub Bot commented on SCM-921:
------------------------------------

jira-importer commented on issue #1149:
URL: https://github.com/apache/maven-scm/issues/1149#issuecomment-2964648711

   **[Michael 
Osipov](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=michael-o)**
 commented
   
   https://tools.ietf.org/html/rfc8089#appendix-E says that drive letters are 
case-insensitive. Again, URI is broken...
   
   Please look at `org.apache.maven.scm.util.FilenameUtilsTest` you can add a 
similar test to the class you have patched.
   




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

Reply via email to