[jbosstools-issues] [JBoss JIRA] (JBIDE-17523) Filter runtime downloads to hide unsupported runtime types

[Rob Stryker (JIRA)]

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

Rob Stryker resolved JBIDE-17523.
---------------------------------

    Resolution: Done


pushed to b3

> Filter runtime downloads to hide unsupported runtime types
> ----------------------------------------------------------
>
>                 Key: JBIDE-17523
>                 URL: https://issues.jboss.org/browse/JBIDE-17523
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: runtime-detection, server
>    Affects Versions: 4.2.0.Beta2
>            Reporter: Martin Malina
>            Assignee: Rob Stryker
>             Fix For: 4.2.0.Beta3
>
>
> This concern arose while testing the new WildFly 8.1 runtime added to stacks.yaml (JDF-727). This itself is ok, but Rob pointed out another concern:
> If a new runtime requires a new runtime type in the future and we add this to stacks.yaml, older versions of JBDS/JBT will not recognize this runtime type, but will still gladly offer it to you for download through Preferences -> Runtime Detection -> Download. When you choose the path of Server -> New, the runtimes offered for download are restricted to the given server type, so we're safe there.
> So this is what we should do:
> The list of runtimes offered for download should always be restricted to only those runtimes that are defined in the given JBDS/JBT.
> E.g. if EAP 7 needs an eap7 runtime type in stacks.yaml, but this type is not available in JBDS 8, JBDS 8 should not offer EAP 7 for download.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)