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

Alex Harui commented on SCM-921:
--------------------------------

After more digging, it turns out that the Jenkins node/slave/agent was set up 
with a lowercase 'c' in its workspace location.  When maven calculates 
subfolder paths, it uses uppercase 'C' and java.net.URI's relativize can't 
handle the different cases.

Interesting side note:  After changing the Jenkins config, the next run failed 
because the basedir now correctly had uppercase 'C' but the path to the pom 
still had lowercase 'c'.  Then after a restart of the server, they both used 
uppercase 'C' and now all files are being committed properly.

> 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
>          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.3.4#803005)

Reply via email to