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

[Nick Boldt (JIRA)]

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

Nick Boldt commented on JBDS-3079:
----------------------------------

Ah, but the installer *is* an update site, and the JBDS IS users have been using it for offline installs because it includes most of what they need to get started w/ JBDS IS.

If we don't fix this, these 3 connectors can't easily be installed into JBDS via offline. 

Or the connectors need to be changed to omit the aforementioned features, which may make them installable but non-functional. 

https://github.com/jbosstools/jbosstools-discovery/blob/master/jbdevstudio/com.jboss.jbds.central.discovery/plugin.xml#L84-L103

https://github.com/jbosstools/jbosstools-discovery/blob/master/jbdevstudio/com.jboss.jbds.central.discovery/plugin.xml#L659-L680

https://github.com/jbosstools/jbosstools-discovery/blob/master/jbdevstudio/com.jboss.jbds.central.discovery/plugin.xml#L438-L468

Alternatively, I could add these features back into the JBDS installer so that they're available for offline Central installs. This is still my preferred solution as it's the least maintenance required between milestones (Central TP doesn't need updating each time we release a milestone).

Or we can go back to option (a), which is to tell people that for Central offline installs, you need: 

* JBDS installer (642 or 504M), 
* Central update site (115M),
AND now as well:
* JBDS update site (855M)

For Beta2, you only needed the installer and Central update site. This change -- losing these three features from the installer jar -- means forcing an additional download onto users. That download is 855M.

I would rather these three tiny features be in the installer, but since Denis rejected that solution in JBDS-3071, I would next rather they be added to the Central site so they can be found offline.

> 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)