[jbosstools-issues] [JBoss JIRA] (JBIDE-20460) Add notion of maximum execution environment for servers

[Rob Stryker (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-20460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rob Stryker reassigned JBIDE-20460:
-----------------------------------

         Assignee: Rob Stryker
    Fix Version/s: 4.3.0.CR1
       Resolution: Done


This has been fixed and added. Unfortunately, since none of our server adapters actually require this feature, it'll be a little hard to test ;) 

[~mmalina] - What you can do is open the class JBossAS6ExtendedProperties   and change the method getMaximumExecutionEnvironment() to read as follows:

{code}
	public IExecutionEnvironment getMaximumExecutionEnvironment() {
		// NEW_SERVER_ADAPTER  Subclasses override this
		return EnvironmentsManager.getDefault().getEnvironment("JavaSE-1.7"); //$NON-NLS-1$
	}
{code}

Then, build the plugins, install them, and try to create an AS6 server in a workspace that only has java8 JREs.  You should see some message like "This server requires an execution environment between JavaSE-1.6 and JavaSE-1.7. Caution is advised."

This message should show whether the user has selected the execution environments or the hard-coded jre options. 

> Add notion of maximum execution environment for servers
> -------------------------------------------------------
>
>                 Key: JBIDE-20460
>                 URL: https://issues.jboss.org/browse/JBIDE-20460
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: server
>    Affects Versions: 4.3.0.CR1
>            Reporter: Rob Stryker
>            Assignee: Rob Stryker
>             Fix For: 4.3.0.CR1
>
>
> FuseIDE has a need for our various runtime composites to warn and properly display valid jre's that are within a range of java versions, rather than just a minimum.  At this point, I do not believe JBT itself has any runtimes that require this functionality, but we may in the future, so this is definitely a valid usecase. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)