[jbosstools-issues] [JBoss JIRA] (JBIDE-18324) Fix Forge setup in JBDS Central
Fred Bricon (JIRA)
issues at jboss.org
Fri Sep 12 14:33:19 EDT 2014
[ https://issues.jboss.org/browse/JBIDE-18324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Fred Bricon updated JBIDE-18324:
--------------------------------
Assignee: Mickael Istria
> Fix Forge setup in JBDS Central
> -------------------------------
>
> Key: JBIDE-18324
> URL: https://issues.jboss.org/browse/JBIDE-18324
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, central, target-platform
> Affects Versions: 8.0.0.CR1
> Reporter: Fred Bricon
> Assignee: Mickael Istria
>
> 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