You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Robert Scholte (JIRA)" <ji...@codehaus.org> on 2013/01/13 14:02:13 UTC
[jira] (SCM-657) SvnExeExportCommand with revision malfunctions for
moved/deleted files
[ https://jira.codehaus.org/browse/SCM-657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte updated SCM-657:
-------------------------------
Component/s: maven-scm-provider-svn
Description:
According to http://subversion.tigris.org/issues/show_bug.cgi?id=2163, which is marked 'INVALID' @revision must be used instead of -r revision, otherwise export does not find specified file.
Attached is a fixed implementation of {{createCommandLine}} method of {{org.apache.maven.scm.provider.svn.svnexe.command.export.SvnExeExportCommand}}
was:
According to http://subversion.tigris.org/issues/show_bug.cgi?id=2163, which is marked 'INVALID' @revision must be used instead of -r revision, otherwise export does not find specified file.
Attached is a fixed implementation of createCommandLine method of org.apache.maven.scm.provider.svn.svnexe.command.export.SvnExeExportCommand
> SvnExeExportCommand with revision malfunctions for moved/deleted files
> -----------------------------------------------------------------------
>
> Key: SCM-657
> URL: https://jira.codehaus.org/browse/SCM-657
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-svn
> Environment: svn, version 1.6.17 (r1128011)
> compiled Nov 19 2011, 08:40:40
> Reporter: adam.kopecky
> Attachments: fixed_method.txt, patch
>
>
> According to http://subversion.tigris.org/issues/show_bug.cgi?id=2163, which is marked 'INVALID' @revision must be used instead of -r revision, otherwise export does not find specified file.
> Attached is a fixed implementation of {{createCommandLine}} method of {{org.apache.maven.scm.provider.svn.svnexe.command.export.SvnExeExportCommand}}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira