[jbosstools-issues] [JBoss JIRA] (JBDS-3149) Fix Forge setup in JBDS Central

[Mickael Istria (JIRA)]

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

Mickael Istria commented on JBDS-3149:
--------------------------------------

Seems like this change https://github.com/jbosstools/jbosstools-discovery/commit/0b701269999d3f87bca7e6883c98804ac7f2e07a contains a fix for this issue.

> Fix Forge setup in JBDS Central
> -------------------------------
>
>                 Key: JBDS-3149
>                 URL: https://issues.jboss.org/browse/JBDS-3149
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Bug
>          Components: central
>    Affects Versions: 8.0.0.CR1
>            Reporter: Fred Bricon
>            Assignee: Fred Bricon
>             Fix For: 8.0.0.CR2
>
>
> Following JBIDE-17690 : 
> [~mickael_istria] said : 
> {quote}You say that since it's already embedded, it should not appear on software page. Then I have the regret to tell you that this is a bad assumption. Things are shown on Central page unless the CONNECTOR is already installed, not its contained IUs. So even if Forge is already included, it is shown anyway. I you need another behaviour, this requires some work on Central.
> I now remember that I had to update the TP on Monday morning before releasing CR1a to add Forge on Discovery. Installation-tests were failing without it: https://github.com/jbosstools/jbosstools-discovery/commit/41885e7e9b2e7ca20ed3dc999820bdcf51e2d9b0 , showing that it was impossible to install Forge in JBDS.
> So this means that not all features from Forge are available in JBDS, and that at least one of them (I don't remember which one-s) need to be added to Discovery site for effective installations.
> {quote}



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)