[jbosstools-issues] [JBoss JIRA] (JBTIS-520) developer urls in our stable stream

[Alexey Kazakov (JIRA)]

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

Alexey Kazakov commented on JBTIS-520:
--------------------------------------

1. Yes, this what is expected. Only one update site is available.
2. There is SOA available. If it's GA ready then it's OK. The rest (not GA ready IS stuff should be available in EA only).
3. This is confusion we have discussed in JBDS-3525 (see the last few comments). We add EA update site only when you installed something from EA. If you just check "Enable EA" in central but didn't really install anything yet from it then we don't add the update site. So, "Show EA" would be better than "Enable EA" actually. We will continue discuss how we can improve EA central in  JBIDE-20609

> developer urls in our stable stream
> -----------------------------------
>
>                 Key: JBTIS-520
>                 URL: https://issues.jboss.org/browse/JBTIS-520
>             Project: JBoss Tools Integration Stack
>          Issue Type: Bug
>          Components: releng
>            Reporter: Max Rydahl Andersen
>            Assignee: Paul Leacu
>            Priority: Blocker
>         Attachments: 1.png, 2.png, 3.png, non-ea.png, non-ea2.png
>
>
> JBDS 9.0 is GA but we still point to /development/ at https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/jbosstools/configuration/ide-config.properties#L210
> earlyaccess is correct, but not the main IS site.
> according to [~akazakov] he verified the dev site is added when installing IS work into JBDS 9.
> Also it shuold not be necessary to use the nested IS site when it should be composited into the main updatesite for release.
> Please make sure we do not cross these streams. 



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)