[
https://issues.jboss.org/browse/JBIDE-14815?page=com.atlassian.jira.plugi...
]
Fred Bricon updated JBIDE-14815:
--------------------------------
Description:
We need to be able to distinguish a gatein runtime from a regular as runtime
Use case : a project example needs to check if GateIn 3.6 is installed
Use case : a project example requires AS7 or EAP6, we want to propose compatible download
runtimes, excluding GateIn
Problem : GateIn runtimes have the same wtp runtime id as as7.
From a project example / stacks perspective, we could define wtp ids
like org.jboss.ide.eclipse.as.runtime.71#gatein-3.5
was:
We need to be able to distinguish a gatein runtime from a regular as runtime
Use case : a project example needs to check if GateIn 3.6 is installed
Use case : a project example requires AS7 or EAP6, we want to propose compatible download
runtimes, excluding GateIn
Problem : GateIn runtimes have the same wtp runtime id as as7.
Find a way to disambiguate different distributions of the same
runtime family
-----------------------------------------------------------------------------
Key: JBIDE-14815
URL:
https://issues.jboss.org/browse/JBIDE-14815
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: server
Affects Versions: 4.1.0.Beta1
Reporter: Fred Bricon
Fix For: 4.1.0.Beta2
We need to be able to distinguish a gatein runtime from a regular as runtime
Use case : a project example needs to check if GateIn 3.6 is installed
Use case : a project example requires AS7 or EAP6, we want to propose compatible download
runtimes, excluding GateIn
Problem : GateIn runtimes have the same wtp runtime id as as7.
From a project example / stacks perspective, we could define wtp ids like
org.jboss.ide.eclipse.as.runtime.71#gatein-3.5
--
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