[
https://issues.jboss.org/browse/JBIDE-20760?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-20760:
------------------------------------
{quote}
(2015-10-01 09:33:02) ldimaggi_: nickboldt, so - we will have the unused and disabled
update site, yes?
(2015-10-01 09:40:31) nickboldt: ldimaggi_: as documented in the JIRA, putting the feature
BACK into the site means when a user installs the eclipse docker tooling feature, they get
added to their list of available update sites in Eclipse (not JBDS) a new, *disabled* URL
for the docker update site
(2015-10-01 09:40:42) nickboldt: ldimaggi_: you already agreed to this in the jira
(2015-10-01 09:40:58) ldimaggi_: nickboldt, +1 just checking
{quote}
Also +1'd by Alexey on the PR, so applied in 4.3.x and building:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
>=123
docker feature not included in Marketplace entry for JBoss Tools
----------------------------------------------------------------
Key: JBIDE-20760
URL:
https://issues.jboss.org/browse/JBIDE-20760
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: marketplace
Affects Versions: 4.3.0.CR1
Reporter: Nick Boldt
Assignee: Nick Boldt
Priority: Blocker
Labels: respin-a
Fix For: 4.3.0.CR2
Attachments: 20760.png
Because we removed the docker feature and replaced it with the docker plugins in order to
avoid the odious problem of a disabled update site appearing in Eclipse's list of
Available Update Sites, we no longer have a way to provide the docker tooling via our
Marketplace entry.
Solution:
1. Stop caring if there's an extra *disabled* update site in Eclipse when we install
JBT (there's a disabled Mylyn one there too, plus 4 enabled ones for Mars, Mylyn,
Eclipse, and WTP, so what's one more?).
2. Use the Docker Tooling feature in JBT's CoreTools category & on the
Marketplace entry (as we did for Beta2).
Then, for JBDS, we continue to just use the plugins and include them in the
com.jboss.devstudio.core.feature so they're installed OOTB via the BYOE / Core feature
(and also via Marketplace).
Sound good?
Alternative solutions:
a. Create a new feature wrapper, just to contain the docker plugins
b. Update some JBT plugins to depend on the docker plugins so they get installed along
with the existing JBT plugin
c. do nothing
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)