[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-8961) Improve the handling of temporary deploy dir

[Rob Stryker (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-8961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12606746#comment-12606746 ] 

Rob Stryker commented on JBIDE-8961:
------------------------------------

As I already said, cloning and overhauling entirely the utility classes in WTP that do the copying is dangerous and will only lead to grief and trouble. Trying to add two SEPARATE behaviors, one as a fallback, will lead to code duplication, be ugly, and actually a little difficult. 

As was said before, in servers that are *NOT* deploy-only servers, there are only three options:  1) deploy to metadata,  2) deploy to server, 3) deploy custom. 

In 1), the deploy folder and temp deploy folder are *GUARANTEED* to be on the same file system. (metadata/plugin/org.jboss.as/servers/a/tmpDeploy vs deploy)
In 2), the deploy folder and temp deploy folder are *GUARANTEED* to be on the same file system. (server/default/deploy vs server/default/tmp/jbt_tmp_deploy)
In 3), the USER must HAND-WRITE both the deploy folder and custom deploy folder. 

So, it is only the deploy-only folder, and the regular servers in custom-mode, that suffer from this issue. 

> 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: http://www.atlassian.com/software/jira