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

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

jira-importer opened a new issue, #928:
URL: https://github.com/apache/maven-scm/issues/928

   **[Felix 
Simmendinger](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=fsimmend)**
 opened 
**[SCM-714](https://issues.apache.org/jira/browse/SCM-714?redirect=false)** and 
commented
   
   The issue from SCM-697 does not solve the issue as the gitprovider is not 
using the add command but the checkin command during a release.
   
   
   ---
   
   **Affects:** 1.8.1
   
   **Issue Links:**
   - [SCM-797](https://issues.apache.org/jira/browse/SCM-797) gitexe checkIn() 
fails due to Windows command line length limitation
    (_**"duplicates"**_)
   - [SCM-697](https://issues.apache.org/jira/browse/SCM-697) git add fail on 
windows when a lot of files to add
   
   
   **Remote Links:**
   - [GitHub Pull Request #30
   ](https://github.com/apache/maven-scm/pull/30)
   - [GitHub Pull Request #41
   ](https://github.com/apache/maven-scm/pull/41)
   - [GitHub Pull Request #71
   ](https://github.com/apache/maven-scm/pull/71)
   
   1 votes, 5 watchers
   




> mvn release:prepare fails if the command line is too long on windows
> --------------------------------------------------------------------
>
>                 Key: SCM-714
>                 URL: https://issues.apache.org/jira/browse/SCM-714
>             Project: Maven SCM (Moved to GitHub Issues)
>          Issue Type: Bug
>          Components: maven-scm-provider-gitexe
>    Affects Versions: 1.8.1
>            Reporter: Felix Simmendinger
>            Assignee: Robert Scholte
>            Priority: Blocker
>
> The issue from SCM-697 does not solve the issue as the gitprovider is not 
> using the add command but the checkin command during a release.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to