[
https://issues.jboss.org/browse/JBIDE-12101?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-12101:
-------------------------------------
my 120 tests for as.test have all passed without any error, so there are no obvious
regressions.
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: 3.4.0.M1
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira