[jbosstools-issues] [JBoss JIRA] (JBIDE-23364) Two different versions of code recommenders and docker tooling in JBT composite site

[Nick Boldt (JIRA)]

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

Nick Boldt edited comment on JBIDE-23364 at 10/19/16 10:08 PM:
---------------------------------------------------------------

Because we also bundle docker tools in the JBT site we have a similar issue with two different versions of docker tooling in the JBT composite site:

!docker_versions.png!

So... we can either start building the JBT site using the MAX TP instead of the MIN TP to avoid this, or, even better, we can remove these features which are duplicated in the TP and the site.

HOWEVER it we remove them from the JBT site, they can't be force-installed via the Marketplace connector or the JBT Abridged "Core Tools" category. But to work around that, we need only have a plugin or feature which DEPENDS on them to cause them to be installed automatically.

[~akazakov] [~jjohnstn] [~mickael_istria] what do you want to do here to avoid this unneeded remediation step when installing JBT? 

A) Build from Max TP [0]? or
B) Remove from JBT update site [1], [2] and introduce feature/plugin dependencies from something in o.j.t.* ?


[0] http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.61.0.AM1-SNAPSHOT/
[1] https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregate/site/category.xml#L276-L279
[2] https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregate/site/category.xml#L324-L334

We'll probably need the same solution in devstudio too [3], [4].

[3] https://github.com/jbdevstudio/jbdevstudio-product/blob/master/site/category.xml#L329-L339
[4] https://github.com/jbdevstudio/jbdevstudio-product/blob/master/site/category.xml#L278-L281

But because we currently build the devstudio site using the MAX TP (so that it's bundled in the installer) we don't have this problem - it's in there twice, but it's the version both times.


was (Author: nickboldt):
Because we also bundle docker tools in the JBT site we have a similar issue with two different versions of docker tooling in the JBT composite site:

!docker_versions.png!

So... we can either start building the JBT site using the MAX TP instead of the MIN TP to avoid this, or, even better, we can remove these features which are duplicated in the TP and the site.

HOWEVER it we remove them from the JBT site, they can't be force-installed via the Marketplace connector or the JBT Abridged "Core Tools" category. But to work around that, we need only have a plugin or feature which DEPENDS on them to cause them to be installed automatically.

[~akazakov] [~jjohnstn] [~mickael_istria] what do you want to do here to avoid this unneeded remediation step when installing JBT? 

A) Build from Max TP [0]? or
B) Remove from JBT update site [1], [2] and introduce feature/plugin dependencies from something in o.j.t.* ?


[0] http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.61.0.AM1-SNAPSHOT/
[1] https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregate/site/category.xml#L276-L279
[2] https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregate/site/category.xml#L324-L334

We'll probably need the same solution in devstudio too [3], [4].

[3] https://github.com/jbdevstudio/jbdevstudio-product/blob/master/site/category.xml#L329-L339
[4] https://github.com/jbdevstudio/jbdevstudio-product/blob/master/site/category.xml#L278-L281


> Two different versions of code recommenders and docker tooling in JBT composite site
> ------------------------------------------------------------------------------------
>
>                 Key: JBIDE-23364
>                 URL: https://issues.jboss.org/browse/JBIDE-23364
>             Project: Tools (JBoss Tools)
>          Issue Type: Sub-task
>          Components: target-platform
>    Affects Versions: 4.4.2.AM2
>            Reporter: Nick Boldt
>            Assignee: Nick Boldt
>             Fix For: 4.4.2.AM3
>
>         Attachments: docker_versions.png, snipmatch_versions.png
>
>
> This remediation error occurs when trying to install JBT 4.4.2.AM2 into Eclipse JEE bundle Neon.1a:
> {code}
> Your original request has been modified.
>   "JavaScript Development Tools" will be ignored because a newer version is already installed. 
>   "Eclipse JSON Editors and Tools" will be ignored because a newer version is already installed. 
>   "WST JSON Core" will be ignored because a newer version is already installed. 
> Cannot complete the install because of a conflicting dependency.
>   Software being installed: Code Recommenders Snipmatch 2.4.0.v20160607-1609 (org.eclipse.recommenders.snipmatch.rcp.feature.feature.group 2.4.0.v20160607-1609)
>   Software currently installed: Code Recommenders for Java Developers 2.4.3.v20160913-0645 (org.eclipse.recommenders.rcp.feature.feature.group 2.4.3.v20160913-0645)
>   Only one of the following can be installed at once: 
>     Code Recommenders Dependency Identification UI 2.4.0.v20160607-1609 (org.eclipse.recommenders.coordinates.rcp 2.4.0.v20160607-1609)
>     Code Recommenders Dependency Identification UI 2.4.3.v20160913-0645 (org.eclipse.recommenders.coordinates.rcp 2.4.3.v20160913-0645)
>   Cannot satisfy dependency:
>     From: Code Recommenders for Java Developers 2.4.3.v20160913-0645 (org.eclipse.recommenders.rcp.feature.feature.group 2.4.3.v20160913-0645)
>     To: org.eclipse.recommenders.coordinates.rcp [2.4.3.v20160913-0645]
>   Cannot satisfy dependency:
>     From: Code Recommenders Snipmatch UI 2.4.0.v20160607-1609 (org.eclipse.recommenders.snipmatch.rcp 2.4.0.v20160607-1609)
>     To: bundle org.eclipse.recommenders.coordinates.rcp [2.4.0,2.4.1)
>   Cannot satisfy dependency:
>     From: Code Recommenders Snipmatch 2.4.0.v20160607-1609 (org.eclipse.recommenders.snipmatch.rcp.feature.feature.group 2.4.0.v20160607-1609)
>     To: org.eclipse.recommenders.snipmatch.rcp [2.4.0.v20160607-1609]{code}



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)