[jbosstools-issues] [JBoss JIRA] (JBIDE-12101) per-module temp deploy folder is not respected
Rob Stryker (JIRA)
jira-events at lists.jboss.org
Thu Sep 20 02:39:34 EDT 2012
[ https://issues.jboss.org/browse/JBIDE-12101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rob Stryker resolved JBIDE-12101.
---------------------------------
Resolution: Done
I made a new commit. My experience was showing me that the temp file was created with a deep path like /my/temp/deploy/someweb.war/someTempFile28343234.txt
Obviously the requirement for someweb.war being there is not needed, and would need to be cleaned up. I have changed this to no longer add the someweb.war in, so you don't have these empty folders sticking around.
I was unable to replicate any FILE sitting around left over. Just empty folders.
> per-module temp deploy folder is not respected
> ----------------------------------------------
>
> Key: JBIDE-12101
> URL: https://issues.jboss.org/browse/JBIDE-12101
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS/Servers
> Affects Versions: 3.3.0.CR1
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.0.0.Alpha2
>
> Attachments: JBIDE-12101.patch
>
>
> Step 1) Create a jboss server
> step 2) create a dynamic web project
> step 3) open server editor for server from 1)
> step 4) set server to view all modules
> step 5) modify the deploy and the temp deploy folders
> step 6) save editor
> step 7) add web project to server, initiate full publish
> step 8) verify whether or not the file copy went to the right temp folder (FAIL)
> Details that will be helpful to actually catching the bug are:
> 1) you will want your server to use server based deployment (middle radio)
> 2) You will want to customize the per-module deploy folder to be on a different file system
> 3) You will want the per-module temp folder to be on the same fs as the per-module deploy folder
> The file-copy mechanism initially copies to the tempDeployFolder, then does a renameTo the final destination. The renameTo fails if the source and destination are on different Filesystems. To force the bug, you will want to ensure the default deploy / temp deploy (in the disabled text boxes) is different from the ones you type in the server editor / column viewer.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbosstools-issues
mailing list