[
https://issues.apache.org/jira/browse/SCM-797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17963122#comment-17963122
]
ASF GitHub Bot commented on SCM-797:
------------------------------------
jira-importer commented on issue #1020:
URL: https://github.com/apache/maven-scm/issues/1020#issuecomment-2964639400
**[Robert
Scholte](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=rfscholte)**
commented
There's a huge difference between adding and committing files. For the first
one it's not a problem to do it file by file (you're just marking them as
committable), but for the latter it is. You want all these files to be part of
the same commit.
So it looks like for Windows it can't be solved properly for commandline
git, but did you try switching to the jgit implementation? See
http://maven.apache.org/scm/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-jgit/index.html
> gitexe checkIn() fails due to Windows command line length limitation
> --------------------------------------------------------------------
>
> Key: SCM-797
> URL: https://issues.apache.org/jira/browse/SCM-797
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Components: maven-scm-provider-gitexe
> Affects Versions: 1.9.4
> Environment: Windows
> Reporter: Radovan Murin
> Assignee: Michael Osipov
> Priority: Critical
> Labels: Maven, SCM
> Fix For: 1.10.0
>
>
> Hello,
> I noticed that for a project with a large amount of pom files the prepare
> command of the release plugin fails when it tries to git add all of the poms.
> The failure happens because the SCM plugin attempts to git add all of the
> files at once which fails on Windows machines due to the command line length
> limitation.
> I have written a small fix and created a pull request
> https://github.com/apache/maven-scm/pull/30
> Basicaly, with the fix, the command git add iterates on all files rather than
> adding them in one command. The fix was already present in the code in
> the GitAddCommand.java. However there was one more place in the code with the
> bug.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
