[jbosstools-issues] [JBoss JIRA] (JBIDE-13441) Changing vm for runtime from default to jdk1.7, then back to default, fails
Rob Stryker (JIRA)
jira-events at lists.jboss.org
Tue Jan 29 04:40:47 EST 2013
Rob Stryker created JBIDE-13441:
-----------------------------------
Summary: Changing vm for runtime from default to jdk1.7, then back to default, fails
Key: JBIDE-13441
URL: https://issues.jboss.org/browse/JBIDE-13441
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 4.0.0.Final
Reporter: Rob Stryker
Assignee: Rob Stryker
Fix For: 4.1.0.Alpha1
0) In workspace, ensure workspace has 1.7 jre, then add a 1.6 jre
1) Create a web app with simple servlet, doGet() has logic: System.out.println(System.getProperty("java.version"));
2) Create server and runtime, keep vm at default for exec env
3) Start server, deploy web app, verify 1.6
4) Shutdown server
5) Switch runtime to use 1.7 jre, finish, then save server editor
6) Start server, verify webapp prints to console 1.7
7) Stop server
8) Edit runtime to use default for 1.6 again
9) finish wizard, save server editor
10) start server, run webapp, verify text says 1.6
FAIL
Step 10 fails, the 1.7 server is still chosen. This is a bug in the UI which is not properly clearing the vm flag, and is only setting it when one is chosen.
--
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