[jira] [Closed] (SCM-449) SvnUpdateCommand is updating all the working copy instead of only the fileSet passed in argument

["Michael Osipov (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SCM-449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Osipov closed SCM-449.
------------------------------
    Resolution: Auto Closed

This issue has been auto closed because it has been inactive for a long period of time. If you think this issue still applies, retest your problem with the most recent version of Maven and the affected component, reopen and post your results.

> SvnUpdateCommand is updating all the working copy instead of only the fileSet passed in argument
> ------------------------------------------------------------------------------------------------
>
>                 Key: SCM-449
>                 URL: https://issues.apache.org/jira/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
>            Priority: Major
>
> {{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 was sent by Atlassian JIRA
(v7.6.3#76005)