[jbosstools-issues] [JBoss JIRA] (JBDS-3079) Offline Central installation misses some JBT bundles

[Mickael Istria (JIRA)]

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

Mickael Istria commented on JBDS-3079:
--------------------------------------

This change seems good to me.
On a long term, I believe the difference between JBT and JBDS discovery start being so important that it would make sense splitting the target-platforms as well and have them using dedicated sites with dedicated content.

> Offline Central installation misses some JBT bundles
> ----------------------------------------------------
>
>                 Key: JBDS-3079
>                 URL: https://issues.jboss.org/browse/JBDS-3079
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: discovery
>    Affects Versions: 8.0.0.Beta2
>            Reporter: Mickael Istria
>            Priority: Minor
>             Fix For: 8.0.0.Beta3
>
>
> Removed items include:
>     org.jboss.tools.vpe.cordovasim.feature (and source)
>     org.jboss.tools.maven.jbosspackaging.feature (and source)
>     org.jboss.tools.common.mylyn.feature (and source)
> Problem w/ removing these is that the JBDS Central plugin.xml requirs all three of them in these connectors:
>     JBoss Hybrid Mobile Tools + CordovaSim
>     JBoss Tools Maven Packaging Configurator
>     Mylyn support for reporting JBoss JIRAs and Red Hat Bugzillas
> So if we remove them, then those connectors can't be installed in JBDS.
> Possible workarounds:
> a) do nothing and accept that for offline installs, you need the update site (not the installer) + central zip; also accept that the installer != update site
> b) put these 3 features in the installer so that the installer contents == the update site contents (except for sources) [I did this in JBDS-3071 but [~dgolovin] reverted it]
> c) move these 3 features into the JBDS TP; this is bad because it creates an ugly dependency chain: JBDS -> JBDS TP -> JBT -> JBT TP... every time JBT rebuilds, we need to update the version of org.jboss.tools.* in the JBDS TP
> d) move these 3 features into the Central TP; this is bad in that as in (c) we would have to keep updating the Central TP each time there's a new JBT release... but we already have this problem because of Arquillian being included in the EA TP.
> Since (b) was rejected, clearly the solution is (d). Or do nothing and annoy offline users with (a). :D



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)