title: maven-release-plugin: Perform fails with 'working directory "...workspace\target\checkout\workspace" does not exist!'
body: <p>I have maven project that fails when release:perform is called, though release;prepare works as expected.</p>
  
  <p>I have found the bug report (below) which certainly seems to resemble the issue I have but not entirely sure I understand the problem:
  <a href="http://jira.codehaus.org/browse/MRELEASE-516" rel="nofollow noreferrer">MRELEASE516</a></p>
  
  <p>The last few lines of output I get:</p>
  
  <pre><code>[INFO] Executing: cmd.exe /X /C "p4 -d E:\hudson\jobs\myHudsonJob\workspace\target\checkout -p 1.1.1.1:1111: client -d myProjectWorkspace-MavenSCM-E:\hudson\jobs\myHudsonJob\workspace\target\checkout"
  [INFO] Executing goals 'deploy'...
  [WARNING] Base directory is a file. Using base directory as POM location.
  [WARNING] Maven will be executed in interactive mode, but no input stream has been configured for this MavenInvoker instance.
  [INFO] ------------------------------------------------------------------------
  [ERROR] BUILD ERROR
  [INFO] ------------------------------------------------------------------------
  [INFO] Error executing Maven.
  
  Working directory "E:\hudson\jobs\myHudsonJob\workspace\target\checkout\workspace" does not exist!
  </code></pre>
  
  <p>From reading the bug report the possible cause of the error is related to my modules' structure, I've tried to outline it below:</p>
  
  <pre>
  /workspace
  |
  |+ pom.xml (root pom whose parent is the build pom, 
  |           calling release:perform on this pom)
  |           [Modules: moduleA and moduleB]
  |
  |- moduleA
     |+ pom.xml (parent is also build pom)
     |+ build/pom.xml (the build pom - no custom parent)
  |- moduleB
     |+ pom.xml (parent is build pom)
  
  </pre>
  
  <p>It seems that the root pom should be in some common directory inside 'workspace' from the error but tried that and doesn't work, nor make sense as to why I need it.</p>
  
  <p>What does the warning <em>Base directory is a file</em> want me to do instead?! It then figures that the base directory is <em>workspace</em> which then means the working directory is not found...any ideas?</p>
  
  <p>Thanks in advance.</p>
  
  <p><strong>EDIT:</strong></p>
  
  <p>Having checked the SCM configuration it all looks ok to me...in each module and the root pom I have:</p>
  
  <pre><code>&lt;scm&gt;
  &lt;connection&gt;
      scm:perforce:1.1.1.1:1111://rootToDirectoryContainingRelevantPom
  &lt;/connection&gt;
  &lt;developerConnection&gt;
      scm:perforce:1.1.1.1:1111://rootToDirectoryContainingRelevantPom
  &lt;/developerConnection&gt;
  &lt;/scm&gt;
  </code></pre>
  
  <p><strong>EDIT 2:</strong></p>
  
  <p>Maybe I have hit <a href="http://jira.codehaus.org/browse/MRELEASE-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&amp;focusedCommentId=205043#action_205043" rel="nofollow noreferrer">MRELEASE-261</a>?</p>