[
https://jira.jboss.org/jira/browse/JBIDE-5791?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen updated JBIDE-5791:
---------------------------------------
Component/s: JBossAS
Fix Version/s: 3.1.0.CR2
Assignee: Rob Stryker
Priority: Critical (was: Major)
Moved to JBIDE since there is no JBDS specific in this issue.
Rob, looks like a rather annoying bug in the new copy/clone setup of configurations ?
Or is it just the ui being wrong calculating the default ?
Referencing custom server config in subdir is not reflected in deploy
and tmp directories
-----------------------------------------------------------------------------------------
Key: JBIDE-5791
URL:
https://jira.jboss.org/jira/browse/JBIDE-5791
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.1.0.CR2
Reporter: Len DiMaggio
Assignee: Rob Stryker
Priority: Critical
Fix For: 3.1.0.CR2
Attachments: jbds_custom1.png, jbds_custom2.png, jbds_custom3.png
To recreate this issue:
1) Make a copy of the server profile into a subdirectory (for example, copy default into
/server/custom/mydefault)
2) Create a server in JBDS using this /server/custom/mydefault server
3) Observe the server's deploy and tmp directories - they will be created in
/server/mydefault
4) To workaround this - see the 3rd screenshot - intuitively, when the user references a
new custom server in a subdir, the deploy and tmp dirs would be in off the same subdir
--
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