]
Max Rydahl Andersen commented on JBIDE-8961:
--------------------------------------------
Why should only deploy-only server has this check?
Seriously - if it is possible for the user to get in this situation (and it obviously is
since we get this exact error (move failed) on the forums again and again) then it should
be fixed.
Problem is that our error UI doesn't *tell* the user what is wrong it just shows the
side effect: "file copy error" which could mean *anything*.
At least if you fall back to do the copy and that succeeded you could very easily create a
marker (if none exist already) that say something like "There is a problem deploying
files to Server X, move fails but copy does - this most likely mean that the temporary
location and deploy location is on different file systems. You can fix it by doing X
(link?), if you don't we will keep attempting to move/copy the files which will have
an impact on performance"
Improve the handling of temporary deploy dir
--------------------------------------------
Key: JBIDE-8961
URL:
https://issues.jboss.org/browse/JBIDE-8961
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.3.0.M1
Environment: eclipse.buildId=M20110210-1200
java.version=1.6.0_24
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=fr_FR
Framework arguments: -product org.eclipse.epp.package.jee.product
Command-line arguments: -os linux -ws gtk -arch x86_64 -product
org.eclipse.epp.package.jee.product
Reporter: Fred Bricon
Assignee: Rob Stryker
Priority: Critical
Fix For: 3.3.0.M2
On linux, having an web project under /home/<username>/workspace/webproject, you
can not deploy it to /opt/deployfolder (assuming the rights are corrects), since, during
the publish operation, the as plugin tries to rename a temporary file from one filesystem
to another.
{noformat}
Publishing failed
Error renaming /home/fbricon/Dev/test/temp/tmp1839894723052933744.MF to
/opt/deploy/web.war/META-INF/MANIFEST.MF
Error renaming /home/fbricon/Dev/test/temp/tmp6164338251434277972.jar to
/opt/deploy/web.war/WEB-INF/lib/utility.jar
{noformat}
The workaround is to define a temp folder on the same fs as the final deploy directory.
However, the average user will have no clue about how to fix it. There should be a sanity
check upon Deploy Only server creation and/or error displayed on the server configuration,
if deployment would fail upon invalid configuration. Providing a Quick fix might be
useful, or not.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: