[jbosstools-issues] [JBoss JIRA] (JBIDE-14297) add missing metadata to stacks.yml

[Rob Stryker (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-14297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12771470#comment-12771470 ] 

Rob Stryker commented on JBIDE-14297:
-------------------------------------

Re-posting snjezana's comment from related jiras:

 Snjezana Peco added a comment - 07/Mar/13 7:48 AM

In order to use stacks.yaml, we have to fix JBIDE-13686.
We also need some other properties in stacks.yaml to download runtimes. They are the following:

    license URL
    size
    disclaimer (true for a community runtime)
    requireSso (if https://github.com/jbosstools/jbosstools-base/pull/50 is applied)

These properties can be added as labels.

JBT runtime IDs:

JBoss AS 3.2-7.1:

org.jboss.ide.eclipse.as.runtime.32
org.jboss.ide.eclipse.as.runtime.40
org.jboss.ide.eclipse.as.runtime.42
org.jboss.ide.eclipse.as.runtime.50
org.jboss.ide.eclipse.as.runtime.51
org.jboss.ide.eclipse.as.runtime.60
org.jboss.ide.eclipse.as.runtime.70
org.jboss.ide.eclipse.as.runtime.71

EAP 4.3-6.1 (EPP, SOA-P, EWP use the same IDs):

org.jboss.ide.eclipse.as.runtime.eap.43
org.jboss.ide.eclipse.as.runtime.eap.50
org.jboss.ide.eclipse.as.runtime.eap.60
org.jboss.ide.eclipse.as.runtime.eap.61

I am not sure if there is a JDF jira related to this issue, but will fix the issue when the JDF team names a label property(ies).

                
> add missing metadata to stacks.yml
> ----------------------------------
>
>                 Key: JBIDE-14297
>                 URL: https://issues.jboss.org/browse/JBIDE-14297
>             Project: Tools (JBoss Tools)
>          Issue Type: Sub-task
>          Components: central, runtime-detection
>            Reporter: Max Rydahl Andersen
>             Fix For: 4.1.0.Beta1
>
>
> Current missing:
>   * license
>   * filesize
>   * matching wtp server id
>   * ... ?

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