[
https://issues.apache.org/jira/browse/SCM-330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17961094#comment-17961094
]
ASF GitHub Bot commented on SCM-330:
------------------------------------
jira-importer opened a new issue, #557:
URL: https://github.com/apache/maven-scm/issues/557
**[Jorgen
Fastrup](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=agentjfp)**
opened
**[SCM-330](https://issues.apache.org/jira/browse/SCM-330?redirect=false)** and
commented
The SVN command generated by the "createCommandLine" method in the
SvnCheckInCommand class does not consider the maximum length of the generated
"svn commit" command line imposed by Windows XP, see
http://support.microsoft.com/kb/830473
If using the SCM-SVN provider implementation as a part of the Maven2 Release
plugin on a windows XP platform and you are trying to commit a lot of modified
pom.xml's the SCM-SVN provider implementation will fail since it does not
consider the maximum length of the generated "svn commit" command line imposed
by the underlying operating system.
We have implemented a temporary fix for this problem in the
"createCommandLine" method of the SvnCheckInCommand class by simply removing
the code line:
SvnCommandLineUtils.addFiles( cl, fileSet.getFiles() );
from the "createCommandLine" method in release 1.0-beta-3.
When studying the implementation of the "createCommandLine" method in
release 1.0 it seems though this new release also has the same problem with
handling "svn commit" command lines of great lengh.
Would it not be possible to have "createCommandLine" method simply generate
an implicit "svn commit" command line and not generate an explicit "svn commit"
as currently implemented ... in this way the length of the commandl ine will
never exceed the limits imposed by say Windows XP ?
Regards
Jorgen Fastrup
---
**Affects:** 1.0-beta-3
> Bug when trying to commit a large number of source files using the SVN
> command line tool as a part of the Maven2 Release plugin
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: SCM-330
> URL: https://issues.apache.org/jira/browse/SCM-330
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Components: maven-scm-provider-svn
> Affects Versions: 1.0-beta-3
> Environment: Windows XP
> Reporter: Jorgen Fastrup
> Priority: Major
>
> The SVN command generated by the "createCommandLine" method in the
> SvnCheckInCommand class does not consider the maximum length of the generated
> "svn commit" command line imposed by Windows XP, see
> http://support.microsoft.com/kb/830473
> If using the SCM-SVN provider implementation as a part of the Maven2 Release
> plugin on a windows XP platform and you are trying to commit a lot of
> modified pom.xml's the SCM-SVN provider implementation will fail since it
> does not consider the maximum length of the generated "svn commit" command
> line imposed by the underlying operating system.
> We have implemented a temporary fix for this problem in the
> "createCommandLine" method of the SvnCheckInCommand class by simply removing
> the code line:
> SvnCommandLineUtils.addFiles( cl, fileSet.getFiles() );
> from the "createCommandLine" method in release 1.0-beta-3.
> When studying the implementation of the "createCommandLine" method in release
> 1.0 it seems though this new release also has the same problem with handling
> "svn commit" command lines of great lengh.
> Would it not be possible to have "createCommandLine" method simply generate
> an implicit "svn commit" command line and not generate an explicit "svn
> commit" as currently implemented ... in this way the length of the commandl
> ine will never exceed the limits imposed by say Windows XP ?
> Regards
> Jorgen Fastrup
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
