Remove setting working directory in export command api. Working directory has no meaning to export command

not sure I want to do this any more, since checkout does support setting working directory but has no need to for it.

Still thinking

after further thinking, i think export does not need to follow checkout to support unused/redundant code. So we should deprecate FileSet argument from the interface. First step to to have mojo to passing null FileSet and have the 2 current export provider ( svn and cvs) to handle null FileSet. Note FileSet is where we passing in working directory which is always exportDirectory

FileSet do have some meaning with Export api

/**

• Create an exported copy of the repository on your local machine
  *
• @param repository the source control system
• @param fileSet the files are copied to the {@link org.apache.maven.scm.ScmFileSet#getBasedir()}

  location

• @return
• @throws ScmException if any
  */
  ExportScmResult export( ScmRepository repository, ScmFileSet fileSet )
  throws ScmException;

so I we cant not get rid of it. I will put it back supporting workingDirectory at Export command level. However at Plugin level, there is no need to passing exportDirectory