title: JBoss Tools deploy error: This may be caused by your server's temporary deploy directory being on a different filesystem than the final destination
body: <p>I have the following error when deploying an application with JBoss Tools in Eclipse:</p>
  
  <blockquote>
    <p>Error renaming C:\wildfly-8.1.0.Final\standalone\tmp\tmp7858611943756287857.xhtml to C:\wildfly-8.1.0.Final\standalone\deployments\.war\403.xhtml.</p>
    
    <p>This may be caused by your server's temporary deploy directory being on a different filesystem than the final destination.</p>
    
    <p>You may adjust these settings in the server editor.</p>
  </blockquote>
  
  <p>And here is a screenshot of the error:</p>
  
  <p><img src="https://i.stack.imgur.com/96PI6.png" alt="JBoss Tools error"></p>
  
  <p>On the <a href="http://docs.jboss.org/tools/4.1.x.Final/en/User_Guide/html_single/index.html#Manage_Server_Settings_in_the_Deployment_Tab" rel="noreferrer">documentation</a>, I found this:</p>
  
  <blockquote>
    <p>You can customize the deployment location and packaging type:</p>
    
    <ul>
    <li>To select the workspace deployment folder for the server, click <em>Use workspace metadata</em>.</li>
    <li>To select the deployment folder of the application server, click <em>Use the JBoss deploy folder</em>.</li>
    <li>To select a folder of your choice, click <em>Use a custom deploy folder</em>. With this option, complete the <em>Deploy directories</em> and <em>Temporary Deploy Directory</em> fields. <strong>The temporary folder must be on the same file system as the final deploy location otherwise publishing often fails</strong>.</li>
    <li>For all modules to be archived for deployment, select the <em>Deploy projects as compressed archives</em> check box. This avoids exploded
    deployments and reduces the amount of memory deployments occupy but
    may result in slower deployment.</li>
    </ul>
  </blockquote>
  
  <p>What does <em>The temporary folder must be on the same file system as the final deploy location</em> mean? How can I solve it?</p>
  
  <p>I've realized that the error doesn't occur when the check box <em>Deploy projects as compressed</em> archives is checked.</p>