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/04/05 21:56:52 UTC
[jira] (SCM-449) SvnUpdateCommand is updating all the working copy
instead of only the fileSet passed in argument
[ https://jira.codehaus.org/browse/SCM-449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte updated SCM-449:
-------------------------------
Description:
{{scmManager.update()}} is updating all the files instead of the files given in parameter:
{code}
lScmFile = new ScmFileSet(basedir, myFile);
lScmResult = scmManager.update(scmRepository, lScmFile);
{code}
Due to the {{SvnUpdateCommand.java}} which is updating all the working copy, not only the {{FileSet}} given in argument. Here an extract of the line {{executeUpdateCommand()}}:
{code}
Commandline cl = createCommandLine( (SvnScmProviderRepository) repo, fileSet.getBasedir(), version );
{code}
Should not we use {{fileSet}} instead of {{fileSet.getBaseDir()}} ?
The {{SvnCheckInCommand()}} is using for instance the {{fileSet}} only
{code}
Commandline cl = createCommandLine( (SvnScmProviderRepository) repo, fileSet, messageFile );
{code}
was:
scmManager.update() is updating all the files instead of the files given in parameter:
lScmFile = new ScmFileSet(basedir, myFile);
lScmResult = scmManager.update(scmRepository, lScmFile);
Due to the SvnUpdateCommand.java which is updating all the working copy, not only the FileSet given in argument. Here an extract of the line executeUpdateCommand():
Commandline cl = createCommandLine( (SvnScmProviderRepository) repo, fileSet.getBasedir(), version );
Should not we use fileSet instead of fileSet.getBaseDir() ?
The SvnCheckInCommand() is using for instance the fileSet only
Commandline cl = createCommandLine( (SvnScmProviderRepository) repo, fileSet, messageFile );
> SvnUpdateCommand is updating all the working copy instead of only the fileSet passed in argument
> ------------------------------------------------------------------------------------------------
>
> Key: SCM-449
> URL: https://jira.codehaus.org/browse/SCM-449
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-svn
> Affects Versions: 1.1
> Environment: maven 2.0.9
> Java 6
> Reporter: Jean-Paul GUIGUI
>
> {{scmManager.update()}} is updating all the files instead of the files given in parameter:
> {code}
> lScmFile = new ScmFileSet(basedir, myFile);
> lScmResult = scmManager.update(scmRepository, lScmFile);
> {code}
> Due to the {{SvnUpdateCommand.java}} which is updating all the working copy, not only the {{FileSet}} given in argument. Here an extract of the line {{executeUpdateCommand()}}:
> {code}
> Commandline cl = createCommandLine( (SvnScmProviderRepository) repo, fileSet.getBasedir(), version );
> {code}
> Should not we use {{fileSet}} instead of {{fileSet.getBaseDir()}} ?
> The {{SvnCheckInCommand()}} is using for instance the {{fileSet}} only
> {code}
> Commandline cl = createCommandLine( (SvnScmProviderRepository) repo, fileSet, messageFile );
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira