[
https://jira.jboss.org/jira/browse/JBIDE-3073?page=com.atlassian.jira.plu...
]
Rob Stryker commented on JBIDE-3073:
------------------------------------
The server has those other paths in case your runtime is in /apps/jboss4.2 and your
deploy directory is in /home/max/deployments. One of the two paths listed in the editor
is the ultimate deploy folder, the other is the temporary deploy folder. The temporary
deploy folder should be used so that the final "move" from temporary location to
final location occurs from two paths on the same file system.
Since your deploy folder can be anywhere, even if its not underneath your app server /
runtime, then the temporary folder must also be global. These paths should be global
since its possible that even after moving a runtime, you want your deploy folder and your
temporary deploy folder to remain the same.
Servers are created with hardcoded paths instead of relative to the
runtime
---------------------------------------------------------------------------
Key: JBIDE-3073
URL:
https://jira.jboss.org/jira/browse/JBIDE-3073
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.0.0.beta1
Reporter: Max Rydahl Andersen
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.0.0.cr1
We cannot do another release where the servers are created with hardcoded full paths
instead of relative to the runtime.
If we interpret the directories as relative (i.e. new File(runtime.getDir(),
server.getDir())) then it will even be fully backwards compatible (at least on windows)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira