[
https://jira.jboss.org/jira/browse/JBIDE-5049?page=com.atlassian.jira.plu...
]
Rob Stryker updated JBIDE-5049:
-------------------------------
Fix Version/s: 3.1.0.CR1
(was: 3.1.0.M4)
Specifying Server JRE via Open Launch Configuration is confusing
----------------------------------------------------------------
Key: JBIDE-5049
URL:
https://jira.jboss.org/jira/browse/JBIDE-5049
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.1.0.M4
Environment: JBoss Tools 3.1 M4
JDK Sun 1.5.0_14
JBoss AS 4.3
Reporter: Vlado Pakan
Assignee: Rob Stryker
Fix For: 3.1.0.CR1
Selecting JRE for server defined within Eclipse server view is confusing. Check these two
scenarios:
1. Define new server with Runtime using JRE 1.5.0
2. Open Launch Configuration of this server, select JRE tab, select JRE 1.6.0 choose
apply and OK.
3. Reopen Open Launch Configuration dialog and JRE 1.5.0 is selected instead JRE 1.6.0
Looks like JRE is always inhereted from Server Runtime settings and not using "Open
Launch Configuration" settings and it's confusing.
1. Define new JBoss EAP 5.0 Runtime. This Runtime needs JRE 1.6 and this JRE is
automatically selected during creation of Runtime as Runtime JRE. There is no possibility
to select JRE 1.5 for JBoss EAP 5.0 Runtime.
2. Select JRE 1.5 as default workspace JRE Windows > Preferences > Java >
Installed JRE's
3. Open Launch Configuration and JRE 1.5 is selected and is also used when server is
started. It brings many errors because JBoss 5.0 runs only with 1.6 JRE
4. Change JRE via OPen Launch Configuration dialog to JRE 1.6 choose Apply and OK.
5. Reopen Open Launch Configuration dialog and JRE was not change it's still JRE 1.5.
It's again quite confusing
6. Change workspace default JRE to JRE 1.6
7. Open Launch Configuration is now using JRE 1.6 and server starts correctly
--
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