[JBoss JIRA] (JBIDE-20747) install-grinder returns a blue ball but fails to install 5 plugins due to missing capability &/or package
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20747?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-20747 at 9/22/15 2:28 PM:
-------------------------------------------------------------
Re: (3)
Your manual test COULD include all "packages" (which I assume to mean features and plugins on the update site) if you uncheck the box for "show only categorized items" and then select all.
(This is also what the p2director install tests do.)
Re: (4) You want your manual install test to report what was installed? Try:
{code}
cd eclipse/plugins; ls -la; cd -
cd eclipse/features; ls -la; cd -
{code}
Or some variation on that.
(The p2director tests report a full list of the IUs to be installed as part of their log.)
To know what is going to be published, look into the /staging/ folders. That's what we publish as a simple copy into /development/.
was (Author: nickboldt):
Re: (3)
Your manual test COULD include all "packages" (which I assume to mean features and plugins on the update site) if you uncheck the box for "show only categorized items" and then select all.
Re: (4) You want your manual install test to report what was installed? Try:
{code}
cd eclipse/plugins; ls -la; cd -
cd eclipse/features; ls -la; cd -
{code}
Or some variation on that.
To know what is going to be published, look into the /staging/ folders. That's what we publish as a simple copy into /development/.
> install-grinder returns a blue ball but fails to install 5 plugins due to missing capability &/or package
> ---------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-20747
> URL: https://issues.jboss.org/browse/JBIDE-20747
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.3.0.CR1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 4.3.1.Final
>
>
> This happened in http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
> {code}
> org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.browsersim.eclipse [1120]
> Unresolved requirement: Require-Bundle: org.jboss.tools.browsersim.ui; bundle-version="3.7.0"
> -> Bundle-SymbolicName: org.jboss.tools.browsersim.ui; bundle-version="3.7.0.CR1-v20150901-2111-B229"; singleton:="true"
> org.jboss.tools.browsersim.ui [1122]
> Unresolved requirement: Require-Bundle: org.eclipse.jetty.websocket.server; bundle-version="[9.0.0,10.0.0)"
> -> Bundle-SymbolicName: org.eclipse.jetty.websocket.server; bundle-version="9.2.13.v20150730"
> org.eclipse.jetty.websocket.server [555]
> Unresolved requirement: Require-Capability: osgi.extender; filter:="(osgi.extender=osgi.serviceloader.registrar)"
> Unresolved requirement: Import-Package: org.eclipse.jetty.websocket.servlet; version="[9.0.0,10.0.0)"
> -> Export-Package: org.eclipse.jetty.websocket.servlet; bundle-symbolic-name="org.eclipse.jetty.websocket.servlet"; bundle-version="9.2.13.v20150730"; version="9.2.13"
> org.eclipse.jetty.websocket.servlet [556]
> Unresolved requirement: Require-Capability: osgi.serviceloader; filter:="(osgi.serviceloader=org.eclipse.jetty.websocket.servlet.WebSocketServletFactory)"; cardinality:="multiple"
> -> Provide-Capability: osgi.serviceloader; osgi.serviceloader="org.eclipse.jetty.websocket.servlet.WebSocketServletFactory"
> {code}
> -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
> Similar problems for other IUs:
> {code}
> org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.cordovasim.eclipse [1163]
> org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.feedhenry.ui [1166]
> org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.livereload.core [1221]
> org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.livereload.ui [1222]
> {code}
> But the job was successful!
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (JBIDE-20747) install-grinder returns a blue ball but fails to install 5 plugins due to missing capability &/or package
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20747?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-20747:
------------------------------------
Re: (3)
Your manual test COULD include all "packages" (which I assume to mean features and plugins on the update site) if you uncheck the box for "show only categorized items" and then select all.
Re: (4) You want your manual install test to report what was installed? Try:
{code}
cd eclipse/plugins; ls -la; cd -
cd eclipse/features; ls -la; cd -
{code}
Or some variation on that.
To know what is going to be published, look into the /staging/ folders. That's what we publish as a simple copy into /development/.
> install-grinder returns a blue ball but fails to install 5 plugins due to missing capability &/or package
> ---------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-20747
> URL: https://issues.jboss.org/browse/JBIDE-20747
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.3.0.CR1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 4.3.1.Final
>
>
> This happened in http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
> {code}
> org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.browsersim.eclipse [1120]
> Unresolved requirement: Require-Bundle: org.jboss.tools.browsersim.ui; bundle-version="3.7.0"
> -> Bundle-SymbolicName: org.jboss.tools.browsersim.ui; bundle-version="3.7.0.CR1-v20150901-2111-B229"; singleton:="true"
> org.jboss.tools.browsersim.ui [1122]
> Unresolved requirement: Require-Bundle: org.eclipse.jetty.websocket.server; bundle-version="[9.0.0,10.0.0)"
> -> Bundle-SymbolicName: org.eclipse.jetty.websocket.server; bundle-version="9.2.13.v20150730"
> org.eclipse.jetty.websocket.server [555]
> Unresolved requirement: Require-Capability: osgi.extender; filter:="(osgi.extender=osgi.serviceloader.registrar)"
> Unresolved requirement: Import-Package: org.eclipse.jetty.websocket.servlet; version="[9.0.0,10.0.0)"
> -> Export-Package: org.eclipse.jetty.websocket.servlet; bundle-symbolic-name="org.eclipse.jetty.websocket.servlet"; bundle-version="9.2.13.v20150730"; version="9.2.13"
> org.eclipse.jetty.websocket.servlet [556]
> Unresolved requirement: Require-Capability: osgi.serviceloader; filter:="(osgi.serviceloader=org.eclipse.jetty.websocket.servlet.WebSocketServletFactory)"; cardinality:="multiple"
> -> Provide-Capability: osgi.serviceloader; osgi.serviceloader="org.eclipse.jetty.websocket.servlet.WebSocketServletFactory"
> {code}
> -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
> Similar problems for other IUs:
> {code}
> org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.cordovasim.eclipse [1163]
> org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.feedhenry.ui [1166]
> org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.livereload.core [1221]
> org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.livereload.ui [1222]
> {code}
> But the job was successful!
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (JBIDE-20760) docker feature not included in Marketplace entry for JBoss Tools
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20760?page=com.atlassian.jira.plugi... ]
Len DiMaggio edited comment on JBIDE-20760 at 9/22/15 2:23 PM:
---------------------------------------------------------------
If the cost of having docker tooling in the marketplace is an unused and disabled update site, I guess it's OK.
was (Author: ldimaggio):
If the cost of having cocker tooling in the marketplace is an unused and disabled update site, I guess it's OK.
> 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
> Fix For: 4.3.0.Final
>
> 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)
10 years, 7 months
[JBoss JIRA] (JBIDE-20760) docker feature not included in Marketplace entry for JBoss Tools
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20760?page=com.atlassian.jira.plugi... ]
Len DiMaggio commented on JBIDE-20760:
--------------------------------------
If the cost of having cocker tooling in the marketplace is an unused and disabled update site, I guess it's OK.
> 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
> Fix For: 4.3.0.Final
>
> 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)
10 years, 7 months
[JBoss JIRA] (JBIDE-20510) org.jboss.tools.jmx.local.ProcessInformationStore doesn't handle spaces in the java.home path
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20510?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-20510:
-------------------------------------
[~mmalina] Your error should change from something like "Cannot run program "C:\Program": CreateProcess error=2, " to something like "Cannot run program "C:\Program Files\Path\To\Java\bin\ps.exe": File Not Found
Basically, it should recognize the full path it's being sent, but error differently.
> org.jboss.tools.jmx.local.ProcessInformationStore doesn't handle spaces in the java.home path
> ----------------------------------------------------------------------------------------------
>
> Key: JBIDE-20510
> URL: https://issues.jboss.org/browse/JBIDE-20510
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx
> Affects Versions: 4.3.0.Beta2
> Environment: Windows 7 x64, Eclipse Mars (4.5.0), Java 1.8.0u51
> Reporter: Daniel Atallah
> Assignee: Rob Stryker
> Priority: Critical
> Labels: respin-a
> Fix For: 4.3.0.CR1
>
>
> org.jboss.tools.jmx.local.ProcessInformationStore.loadProcessStore:97 should either use the Runtime.getRuntime().exec(String[]) method to deal with Java installation locations containing spaces.
> In my case the {{java.home}} system property points to {{"C:\Program Files\Java\jdk1.8.0_51"}}, which I think would be pretty normal on Windows.
> {noformat}
> java.io.IOException: Cannot run program "C:\Program": CreateProcess error=2, The system cannot find the file specified
> at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048)
> at java.lang.Runtime.exec(Runtime.java:620)
> at java.lang.Runtime.exec(Runtime.java:450)
> at java.lang.Runtime.exec(Runtime.java:347)
> at org.jboss.tools.jmx.local.ProcessInformationStore.loadProcessStore(ProcessInformationStore.java:97)
> at org.jboss.tools.jmx.local.ProcessInformationStore.refreshProcessInformationStore(ProcessInformationStore.java:64)
> at org.jboss.tools.jmx.local.ProcessInformationStore$1.run(ProcessInformationStore.java:135)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: java.io.IOException: CreateProcess error=2, The system cannot find the file specified
> at java.lang.ProcessImpl.create(Native Method)
> at java.lang.ProcessImpl.<init>(ProcessImpl.java:386)
> at java.lang.ProcessImpl.start(ProcessImpl.java:137)
> at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029)
> ... 7 more
> {noformat}
> I'm note sure what the impact is - I don't necessarily notice anything not working.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (JBIDE-20760) docker feature not included in Marketplace entry for JBoss Tools
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20760?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-20760:
-------------------------------
Description:
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 which contains the docker plugins
b. Update some JBT plugins to depend on the docker plugins
was:
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?
> 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
> Fix For: 4.3.0.Final
>
> 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 which contains the docker plugins
> b. Update some JBT plugins to depend on the docker plugins
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (JBIDE-20760) docker feature not included in Marketplace entry for JBoss Tools
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20760?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-20760:
-------------------------------
Description:
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
was:
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 which contains the docker plugins
b. Update some JBT plugins to depend on the docker plugins
> 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
> Fix For: 4.3.0.Final
>
> 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)
10 years, 7 months
[JBoss JIRA] (JBIDE-20760) docker feature not included in Marketplace entry for JBoss Tools
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20760?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-20760:
-------------------------------
Attachment: 20760.png
> 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
> Fix For: 4.3.0.Final
>
> 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:
> 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?), and just use the feature in JBT's CoreTools category & on the Marketplace entry.
> 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?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (JBIDE-20760) docker feature not included in Marketplace entry for JBoss Tools
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20760?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-20760:
-------------------------------
Description:
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?
was:
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:
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?), and just use the feature in JBT's CoreTools category & on the Marketplace entry.
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?
> 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
> Fix For: 4.3.0.Final
>
> 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?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months