[ 
https://issues.apache.org/jira/browse/SCM-797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Scholte updated SCM-797:
-------------------------------
    Comment: was deleted

(was: michael-o commented on issue #49: SCM-797: Workaround for Windows command 
line length limitation
URL: https://github.com/apache/maven-scm/pull/49#issuecomment-388227873
 
 
   @atomicknight  Please close this has been merged.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]
)

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

Reply via email to