[
https://issues.jboss.org/browse/JBIDE-8961?page=com.atlassian.jira.plugin...
]
Rob Stryker commented on JBIDE-8961:
------------------------------------
So you want an error marker added *in addition* to the rename error that pops up?
Isn't that a bit too much?
Ideally an error marker would not go on a project, as that's kinda nonsensical...
There's nothing wrong with the project, but with the server. Also, not every IModule
is guaranteed an IResource (some may represent out of workspace entities), etc. But
markers can only go on IResource objects, and an IServer is not an IResource, nor does it
necessarily have an IResource backing it.
I made another adjustment to the actual error status object, so now the dialog that pops
up with the error says the following:
PublishRenameFailure=Error renaming {0} to {1}. \n\nThis may be caused by your
server's temporary deploy directory being on a different filesystem than the final
destination.\n\nYou may adjust these settings in the server editor.
Also, lets not forget this error ALSO will appear in the server log view, and,
furthermore, it will appear in the error log if the user's settings designate it to.
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
Attachments: JBIDE-8961.png
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:
http://www.atlassian.com/software/jira