[jbosstools-issues] [JBoss JIRA] Commented: (JBDS-852) Runtime setup should use Java Execution Environment instead of specific VM

[Rob Stryker (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBDS-852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12511952#action_12511952 ] 

Rob Stryker commented on JBDS-852:
----------------------------------

The way the servers are now coded, each runtime type (eap 5.0,  jboss 4.2, jboss 5.0, etc) have a default "execution environment".  As of now this cannot change (except through API if necessary), but this should not need to change, as we all know jboss 4.2 runs on a java 1.4 execution environment, and eap 5.0 runs on a jdk 6.0 execution environment.

So what the code does is first check if there is a persisted (property) for a vm install, or a vm install type.  If neither of these are found, It gets the execution environment for the runtime, which I've already pointed out is hard-coded based on JBoss version and type. So in the case of an EAP 5.0 server, if you simply do not set the vm_install variable, it will default to look for the jdk 6 execution environment.

If there are any valid VMs, it will then run. If there are not, it should not run, however the moment the user installs a JDK that fits into the execution environment, it should immediately run without any further configuration. 

You can look at http://fisheye.jboss.org/browse/~raw,r=20009/JBossTools/trunk/as/plugins/org.jboss.ide.eclipse.as.core/jbosscore/org/jboss/ide/eclipse/as/core/server/internal/LocalJBossServerRuntime.java   for more information, focussing on the getVM() method. 

> Runtime setup should use Java Execution Environment instead of specific VM
> --------------------------------------------------------------------------
>
>                 Key: JBDS-852
>                 URL: https://jira.jboss.org/jira/browse/JBDS-852
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Sub-task
>          Components: installer
>            Reporter: Max Rydahl Andersen
>            Assignee: Denis Golovin
>            Priority: Critical
>             Fix For: 3.0.0.CR2
>
>
> if installer warns and server can be updated to a jdk6 then this issue is less important.
> But if easy to do an using a execution environment will work then we should definitively do that (much more portable)

-- 
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