JBoss Tools deploy error: This may be caused by your server's temporary deploy directory being on a different filesystem than the final destination

[cassiomolin]

I'm having the following error when deploying an application with JBoss Tools:

Error renaming C:\wildfly-8.1.0.Final\standalone\tmp\tmp7858611943756287857.xhtml to C:\wildfly-8.1.0.Final\standalone\deployments\<war-name>.war\403.xhtml.
This may be caused by your server's temporary deploy directory being on a different filesystem than the final destination.
You may adjust these settings in the server editor.

And here is a screenshot from the error:

On the docs available in this link, I've found this:

You can customize the deployment location and packaging type:

• To select the workspace deployment folder for the server, click Use workspace metadata.
• To select the deployment folder of the application server, click Use the JBoss deploy folder.
• To select a folder of your choice, click Use a custom deploy folder. With this option, complete theDeploy directories and Temporary Deploy Directory fields. The temporary folder must be on the same file system as the final deploy location otherwise publishing often fails.
• For all modules to be archived for deployment, select the Deploy projects as compressed archives check box. This avoids exploded deployments and reduces the amount of memory deployments occupy but may result in slower deployment.

What's the meaning of The temporary folder must be on the same file system as the final deploy location?
How can I solve this error?

I realized that the error doesn't occur when the check box Deploy projects as compressed archives is checked.

I also asked the same question at StackOverflow.

[rob.stryker]

To copy files into your deployments folder, we first copy it to a temporary folder (In your case C:\wildfly-8.1.0.Final\standalone\tmp\)  and then attempt to do a file.renameTo(new path).   This command can fail if for example you mark your temporary folder as d:\tmp  and your deployments folder as C:\wildfly-8.1.0.Final\standalone\deployments.

This doesn't appear to be the case in your example, though. So far we haven't had anyone report this issue (at least in this release) so I think it'd be best if we opened a jira to track it and make sure it gets tested by others.

Some possible things that you could do to help us debug it, though, are, after you replicate, can you verify:

  1)  C:\wildfly-8.1.0.Final\standalone\deployments\<war-name>.war    exists, and

2) C:\wildfly-8.1.0.Final\standalone\deployments\<war-name>.war  is not a file / war archive, but is in fact a folder

Obviously we should be able to handle either issue, but, it's always possible that there's a bug somewhere that simply wasn't caught, which would be sad.

I've opened [JBIDE-18697] Error deploying exploded war on windows; fs / copy error - JBoss Issue Tracker to help track the issue.

[cassiomolin]

Thanks, Rob Stryker.

I'm sure C:\wildfly-8.1.0.Final\standalone\deployments\<war-name>.war is a folder, not a file.

I updated [JBIDE-18697] Error deploying exploded war on windows; fs / copy error with the steps to reproduce the issue.