You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jorgen Fastrup (JIRA)" <ji...@codehaus.org> on 2007/07/26 10:06:13 UTC

[jira] Created: (SCM-330) 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

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: http://jira.codehaus.org/browse/SCM-330
             Project: Maven SCM
          Issue Type: Bug
          Components: maven-scm-provider-svn
    Affects Versions: 1.0-beta-3
         Environment: Windows XP
            Reporter: Jorgen Fastrup


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 is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Commented: (SCM-330) 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

Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/SCM-330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=199864#action_199864 ] 

Olivier Lamy commented on SCM-330:
----------------------------------

this can be fixed by using the svnjava provider.

> 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: http://jira.codehaus.org/browse/SCM-330
>             Project: Maven SCM
>          Issue Type: Bug
>          Components: maven-scm-provider-svn
>    Affects Versions: 1.0-beta-3
>         Environment: Windows XP
>            Reporter: Jorgen Fastrup
>
> 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 is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira