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

Mickael Istria (JIRA) issues at jboss.org
Mon Sep 15 10:26:03 EDT 2014


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

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

Actually, issue is not in Central, but in discovery catalog: discovery references org.jboss.tools.forge.ext.feature which is not part of JBoss Developer Studio. So it shows this connector as installable because there is still one feature to install.
Installation status is actually already working as expected: https://github.com/jbosstools/jbosstools-central/blob/jbosstools-4.2.x/central/plugins/org.jboss.tools.central/src/org/jboss/tools/central/editors/xpl/DiscoveryViewer.java#L1196

> 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: Mickael Istria
>             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)


More information about the jbosstools-issues mailing list