[
https://jira.jboss.org/browse/JBIDE-6312?page=com.atlassian.jira.plugin.s...
]
Jiri Peterka commented on JBIDE-6312:
-------------------------------------
I guess I found cause for this problem. When you edit Deployment setting on jboss-eap
editor -> deployment tab and in that time you add new project (jsf project for example)
changes are saved but after reopening previous setting which is wrong is kept. So adding
new projects somehow restores old deployment setting.
JBoss Server doesn't reflect setting on Server Deployment tab
-------------------------------------------------------------
Key: JBIDE-6312
URL:
https://jira.jboss.org/browse/JBIDE-6312
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.1.0.GA
Environment: JBT 3.1.0 GA
Reporter: Jiri Peterka
Assignee: Rob Stryker
Fix For: 3.2.0.M2
Steps:
1. Have EAP 5.0 Server defined in Servers view
2. In Local Deployment (Double click on server -> Deployment tab) set workspace
metadata as deploy server
3. Start server, deploy, undeploy
4. Stop server
5 Set custom folder as default deploy folder, start server, deploy
Change isn't reflected. Application isn't deployed according custom folder
selection. My experience is this setting works very unreliably if ever.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira