[jbosstools-issues] [JBoss JIRA] (JBIDE-13656) New project dialog from central does not reflect runtimes defined in stacks.yaml

[Max Rydahl Andersen (JIRA)]

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

Max Rydahl Andersen updated JBIDE-13656:
----------------------------------------

    Fix Version/s: 4.1.0.Alpha2
                       (was: 4.1.0.Alpha1)


not blocking alpha1 imo.

the PR from snjezana does not fix this issue it just work around it once more by adding more data to the projectexamples instead of actuallly using what is in stacks.yml afaics.
                
> New project dialog from central does not reflect runtimes defined in stacks.yaml
> --------------------------------------------------------------------------------
>
>                 Key: JBIDE-13656
>                 URL: https://issues.jboss.org/browse/JBIDE-13656
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: central
>    Affects Versions: 4.0.0.Final, 4.1.0.Alpha1
>         Environment: JBDS 7.0.0.Alpha1b
>            Reporter: Martin Malina
>            Assignee: Fred Bricon
>             Fix For: 4.0.0.Final, 4.1.0.Alpha2
>
>
> This is a follow-up of JDF-216.
> They created a new branch of jdf-stacks to test EAP 6.1. But even if I used that branch using
> -Dorg.jboss.examples.stacks.url=https://raw.github.com/jboss-jdf/jdf-stack/eap6.1/stacks.yaml
> I am still told that the required runtime is not defined and that I need to have EAP 6 or AS 7.
> The dialog should take advantage of the information provided by stacks.yaml and notice that the correct server is defined.
> See JDF-216 for more details.

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