[
http://jira.codehaus.org/browse/MRELEASE-175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_93332
]
Emmanuel Venisse commented on MRELEASE-175:
-------------------------------------------
no, we can't because I'm sure some SCM need a files list but for svn we can use
--targets argument on svn commit.
I'll fix it in Maven-SCM
> Svn commit fails due to large number of poms on windows
> -------------------------------------------------------
>
> Key: MRELEASE-175
> URL: http://jira.codehaus.org/browse/MRELEASE-175
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: scm
> Affects Versions: 2.0-beta-4
> Environment: windows
> Reporter: Dan Tran
> Fix For: 2.0-beta-5
>
>
> I have so many projects under one source tree that release:prepare fails when
> trying to commit the
> changed pom files ( ie svn command is too long)
> Can we just issue "svn commit" ? This problem hits all scm types on windows
> platform
--
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
