[JBoss JIRA] (JBIDE-21117) Livereload tests fail after migration to jetty 9.3.5
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21117?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-21117:
----------------------------------
Fix Version/s: 4.4.0.Alpha1
> Livereload tests fail after migration to jetty 9.3.5
> ----------------------------------------------------
>
> Key: JBIDE-21117
> URL: https://issues.jboss.org/browse/JBIDE-21117
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: livereload
> Affects Versions: 4.4.0.Alpha1
> Reporter: Denis Golovin
> Fix For: 4.4.0.Alpha1
>
>
> {code}Results :
> Failed tests:
> LiveReloadServerTestCase.shouldForwardRequestOnProxiedServerWithScriptInjectionAndDefaultCharset:845
> Expecting:
> <"">
> to contain:
> <"Hello, World!">
> LiveReloadServerTestCase.shouldForwardRequestOnProxiedServerWithScriptInjectionAndCustomCharset:872
> Expecting:
> <"">
> to contain:
> <"Hello, World!">
> Tests run: 97, Failures: 2, Errors: 0, Skipped: 0
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] jbosstools-livereload .............................. SUCCESS [ 0.286 s]
> [INFO] livereload.plugins ................................. SUCCESS [ 0.008 s]
> [INFO] org.jboss.tools.livereload.core .................... SUCCESS [ 4.714 s]
> [INFO] org.jboss.tools.livereload.ui ...................... SUCCESS [ 0.620 s]
> [INFO] livereload.tests ................................... SUCCESS [ 0.007 s]
> [INFO] org.jboss.tools.livereload.test .................... FAILURE [04:39 min]
> [INFO] livereload.features ................................ SKIPPED
> [INFO] org.jboss.tools.livereload.feature ................. SKIPPED
> [INFO] org.jboss.tools.livereload.test.feature ............ SKIPPED
> [INFO] livereload.site .................................... SKIPPED
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 06:09 min
> [INFO] Finished at: 2015-11-20T09:21:23-08:00
> [INFO] Final Memory: 117M/2226M
> [INFO] ------------------------------------------------------------------------{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21105) Remove BIRT?
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21105?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-21105:
------------------------------------
{quote}(2015-11-20 10:59:42) nickboldt: do you want me to try to include the 9.3.5 versions of the two plugins that Birt needs, instead of the 9.2.9 versions?
(2015-11-20 11:01:58) akazakov: nickboldt, yes
(2015-11-20 11:02:34) akazakov: nickboldt, I just doubt that 9.2.9 and 9.3.5 can so-exist safely
(2015-11-20 11:03:05) nickboldt: akazakov: well, it's only 2 plugins
(2015-11-20 11:03:44) nickboldt: and we (anything in JBT/JBDS) don't depend on jetty.osgi.boot or jetty.deploy... it's just birt that needs them
(2015-11-20 11:03:51) nickboldt: but I can see if moving to 9.3.5 works{quote}
PR:
https://github.com/jbosstools/jbosstools-target-platforms/pull/180
p2diff:
{code}
$➔ p2diff http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.6... file://`pwd`/jbosstools/multiple/target/jbosstools-multiple.target.repo
< org.eclipse.jetty.deploy [9.2.9.v20150224]
< org.eclipse.jetty.osgi.boot [9.2.9.v20150224]
> org.eclipse.jetty.deploy [9.3.5.v20151012]
> org.eclipse.jetty.osgi.boot [9.3.5.v20151012]
> org.eclipse.jetty.plus [9.3.5.v20151012]
> org.eclipse.jetty.annotations [9.3.5.v20151012]
> org.eclipse.jetty.jndi [9.3.5.v20151012]
=== Summary ===
http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.6... contains 2 unique IUs
file:///home/nboldt/tru/targetplatforms/jbosstools/multiple/target/jbosstools-multiple.target.repo contains 5 unique IUs
{code}
> Remove BIRT?
> ------------
>
> Key: JBIDE-21105
> URL: https://issues.jboss.org/browse/JBIDE-21105
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: birt, target-platform
> Affects Versions: 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.0.Alpha1
>
> Attachments: birt-4.5-vs-mars-interim.txt, birt-4.5-vs-mars-interim_summary.txt, birt-depends-on-jetty-deploy-929.png, birt-depends-on-jetty-osgi-boot-929.png, birt-wizard-new-library.png, birt-wizard-new-library__NEON.png, birt-wizards.png, birt-wizards__NEON.png, eclipse-after-birt.png, install-jboss-birt-sites.png, install-jboss-birt-sites__NEON.png, install-jboss-birt.png, install-jboss-birt__NEON.png
>
>
> {quote}
> (2015-11-17 11:42:50) kmarmaliykov: nickboldt: I look into neon M3 and see that there is no jetty 9.2.9 there
> (2015-11-17 11:43:18) nickboldt: kmarmaliykov: yes, 9.2.9 is from Birt site
> (2015-11-17 11:43:21) nickboldt: because Birt needs it
> (2015-11-17 11:43:33) nickboldt: but there's no Birt for Neon yet so we have to include the Birt for Mars
> (2015-11-17 11:43:37) maxandersen: nickboldt: akazakov: are you talking about having birt in Neon ?
> (2015-11-17 11:43:44) maxandersen: afaik birt is dead.
> (2015-11-17 11:43:53) maxandersen: won't participate in neon release afaik.
> (2015-11-17 11:43:56) nickboldt: maxandersen: so we should remove birt from JBT 4.4?
> (2015-11-17 11:44:24) maxandersen: well, check first if birt is actually in neon. if it is not the decision is very easy.
> (2015-11-17 11:44:38) akazakov: +1
> (2015-11-17 11:45:36) maxandersen: if it is in, then lets talk options. but if birt requires us to jump through too many hoops its not worth keeping it in.
> (2015-11-17 11:45:55) nickboldt: birt 4.5.0.v201506092134 is in Neon from 201511131000 (M3) - http://download.eclipse.org/releases/neon/201511131000/
> (2015-11-17 11:47:08) nickboldt: and there's a newer birt 4.5.0.v201510231925 (same major.minor.service, newer datestamp) in http://download.eclipse.org/birt/update-site/mars-interim/
> {quote}
> So, yesterday as part of updates for JBIDE-20976, I pulled a new BIRT mirror here:
> http://download.jboss.org/jbosstools/updates/requirements/birt/4.5.0.v201...
> But we could also just use the old one from Mars.0:
> http://download.jboss.org/jbosstools/updates/requirements/birt/4.5.0.v201...
> Or we could remove support for BIRT and its webtools / charting integration entirely from JBT 4.4.0.Alpha1, since as Max says BIRT is at EOL.
> *DISCUSS*.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21116) XML Configuration and Filesets nodes leak to non-JBoss server adapters
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21116?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-21116:
--------------------------------
Fix Version/s: 4.3.1.Beta1
> XML Configuration and Filesets nodes leak to non-JBoss server adapters
> ----------------------------------------------------------------------
>
> Key: JBIDE-21116
> URL: https://issues.jboss.org/browse/JBIDE-21116
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift, server
> Affects Versions: 4.3.0.Final
> Reporter: Fred Bricon
> Fix For: 4.3.1.Beta1
>
>
> The XML Configuration and Filesets nodes provided by JBoss Tools leak to non-JBoss server adapters.
> !http://content.screencast.com/users/fbricon/folders/Jing/media/be573a07-eff4-4c75-90a0-7334cabb0e09/00000228.png|width=450!
> I find these confusing. After [~rob.stryker] explained me how they work, I can see some value in it, however, I think they should be added to non-JBoss servers on an opt-in basis.
> [~maxandersen] wdyt?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21116) XML Configuration and Filesets nodes leak to non-JBoss server adapters
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21116?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-21116:
--------------------------------
Component/s: openshift
> XML Configuration and Filesets nodes leak to non-JBoss server adapters
> ----------------------------------------------------------------------
>
> Key: JBIDE-21116
> URL: https://issues.jboss.org/browse/JBIDE-21116
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift, server
> Affects Versions: 4.3.0.Final
> Reporter: Fred Bricon
> Fix For: 4.3.1.Beta1
>
>
> The XML Configuration and Filesets nodes provided by JBoss Tools leak to non-JBoss server adapters.
> !http://content.screencast.com/users/fbricon/folders/Jing/media/be573a07-eff4-4c75-90a0-7334cabb0e09/00000228.png|width=450!
> I find these confusing. After [~rob.stryker] explained me how they work, I can see some value in it, however, I think they should be added to non-JBoss servers on an opt-in basis.
> [~maxandersen] wdyt?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21116) XML Configuration and Filesets nodes leak to non-JBoss server adapters
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21116?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-21116:
-------------------------------------
So after some investigation, I've found the following:
1) The nodes are opt-in, not opt-out.
2) We automatically opt-in all org.eclipse.jst.* inside ExtendedServerPropertiesAdapterFactory, for convenience
3) Openshift has opted in by providing an OpenShiftServerExtendedProperties class. The OpenShiftServer implements IExtendedPropertiesProvider. The OpenShiftServerExtendedProperties class can further opt out by overriding allowConvenienceEnhancements() and returning false. This method is currently used only by the xml and fileset nodes.
4) a number of smaller bugs were found with the functionality during this review:
a) two instances of "new Shell()" which used to function properly, now cause a blank shell window to appear somewhere uselessly.
b) a bad iterator index (loop always using result[0] instead of result[i]) means most auto-completion options are not showing
c) an NPE probably caused by a regression and insufficient testing causes autocomplete to fail entirely.
> XML Configuration and Filesets nodes leak to non-JBoss server adapters
> ----------------------------------------------------------------------
>
> Key: JBIDE-21116
> URL: https://issues.jboss.org/browse/JBIDE-21116
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: server
> Affects Versions: 4.3.0.Final
> Reporter: Fred Bricon
>
> The XML Configuration and Filesets nodes provided by JBoss Tools leak to non-JBoss server adapters.
> !http://content.screencast.com/users/fbricon/folders/Jing/media/be573a07-eff4-4c75-90a0-7334cabb0e09/00000228.png|width=450!
> I find these confusing. After [~rob.stryker] explained me how they work, I can see some value in it, however, I think they should be added to non-JBoss servers on an opt-in basis.
> [~maxandersen] wdyt?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21116) XML Configuration and Filesets nodes leak to non-JBoss server adapters
by Fred Bricon (JIRA)
Fred Bricon created JBIDE-21116:
-----------------------------------
Summary: XML Configuration and Filesets nodes leak to non-JBoss server adapters
Key: JBIDE-21116
URL: https://issues.jboss.org/browse/JBIDE-21116
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: server
Affects Versions: 4.3.0.Final
Reporter: Fred Bricon
The XML Configuration and Filesets nodes provided by JBoss Tools leak to non-JBoss server adapters.
!http://content.screencast.com/users/fbricon/folders/Jing/media/be573a07-eff4-4c75-90a0-7334cabb0e09/00000228.png|width=450!
I find these confusing. After [~rob.stryker] explained me how they work, I can see some value in it, however, I think they should be added to non-JBoss servers on an opt-in basis.
[~maxandersen] wdyt?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-20976) Create and use Neon M4 target platform (was: Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20976?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-20976:
-------------------------------
Summary: Create and use Neon M4 target platform (was: Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9) (was: Create and use Neon M3 target platform (was: Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9))
> Create and use Neon M4 target platform (was: Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9)
> --------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-20976
> URL: https://issues.jboss.org/browse/JBIDE-20976
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform, upstream
> Affects Versions: 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 4.4.0.Alpha1
>
> Attachments: features_Mars.0-vs.1.vs.NeonM2.png.png, JBIDE20976_NeonM2.png, JBIDE20976_NeonM2_sapphire.png, p2diff-all.txt, p2diff-summary.txt, p2diff.central.summary.txt, p2diff.central.txt, p2diff.ea.summary.txt, p2diff.ea.txt, p2diff.jbdevstudio_v2.txt, p2diff.jbosstools.txt, plugins_Mars.0-vs.1.vs.NeonM2.png, versionwatch-features.png, versionwatch-plugins.png
>
>
> Opened in JBIDE (not JBDS) because the TPs are essentially the same, so this affects both JBT and JBDS.
> Could be a problem w/ the .target files, or a problem upstream w/ Eclipse projects in Neon not being updated from Mars.0 to their Mars.1 version (or newer).
> Details in these logs:
> http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.vers...
> http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.vers...
> Affected IUs (now sorted alphabetically):
> {code}
> org.eclipse.core.runtime 3.11.1.v20150903-1804
> org.eclipse.egit 4.0.2.201509141540-r
> org.eclipse.egit.core 4.0.2.201509141540-r
> org.eclipse.egit.doc 4.0.2.201509141540-r
> org.eclipse.egit.ui 4.0.2.201509141540-r
> org.eclipse.equinox.p2.rcp.feature 1.2.101.v20150826-1318
> org.eclipse.equinox.p2.user.ui 2.2.101.v20150826-1318
> org.eclipse.jdt 3.11.1.v20150904-0015
> org.eclipse.jdt.doc.user 3.11.1.v20150819-1130
> org.eclipse.jetty.webapp 9.2.13.v20150730
> org.eclipse.jetty.xml 9.2.13.v20150730
> org.eclipse.jgit 4.0.2.201509141540-r
> org.eclipse.jgit.archive 4.0.2.201509141540-r
> org.eclipse.jst.common.frameworks 1.1.701.v201509021802
> org.eclipse.jst.server.tomcat.core 1.1.701.v201508232356
> org.eclipse.jst.web_core.feature 3.7.1.v201509021802
> org.eclipse.jst.web_ui.feature 3.7.1.v201509021802
> org.eclipse.jst.webpageeditor.feature 2.7.1.v201508270443
> org.eclipse.pde 3.11.1.v20150904-0345
> org.eclipse.pde.doc.user 3.11.1.v20150903-1352
> org.eclipse.platform 4.5.1.v20150904-0015
> org.eclipse.platform.doc.user 4.5.1.v20150819-1130
> org.eclipse.rcp 4.5.1.v20150904-0015
> org.eclipse.sapphire 9.0.1.201509151939
> org.eclipse.sapphire.java 9.0.1.201509151939
> org.eclipse.sapphire.java.jdt 9.0.1.201509151939
> org.eclipse.sapphire.java.jdt.ui 9.0.1.201509151939
> org.eclipse.sapphire.modeling 9.0.1.201509151939
> org.eclipse.sapphire.modeling.xml 9.0.1.201509151939
> org.eclipse.sapphire.osgi 9.0.1.201509151939
> org.eclipse.sapphire.osgi.fragment 9.0.1.201509151939
> org.eclipse.sapphire.platform 9.0.1.201509151939
> org.eclipse.sapphire.ui 9.0.1.201509151939
> org.eclipse.sapphire.ui.swt.gef 9.0.1.201509151939
> org.eclipse.sapphire.ui.swt.xml.editor 9.0.1.201509151939
> org.eclipse.sapphire.workspace 9.0.1.201509151939
> org.eclipse.sapphire.workspace.ui 9.0.1.201509151939
> org.eclipse.swt 3.104.1.v20150825-0743
> org.eclipse.wst.common_core.feature 3.7.1.v201508262220
> org.eclipse.wst.common_ui.feature 3.7.1.v201508262220
> org.eclipse.wst.jsdt.feature 1.6.201.v201508262249
> org.eclipse.wst.server.core 1.7.0.v201508271522
> org.eclipse.wst.server.discovery 1.1.0.v201508271522
> org.eclipse.wst.server.ui 1.5.201.v201509022125
> org.eclipse.wst.server_core.feature 3.3.600.v201508271522
> org.eclipse.wst.server_ui.feature 3.3.600.v201509022125
> org.eclipse.wst.validation 1.2.700.v201508251749
> org.eclipse.wst.web_core.feature 3.7.1.v201508271605
> org.eclipse.wst.web_ui.feature 3.7.1.v201509022125
> org.eclipse.wst.ws_ui.feature 3.7.1.v201508271926
> org.eclipse.wst.xml_ui.feature 3.7.1.v201508271605
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-20976) Create and use Neon M3 target platform (was: Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20976?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-20976:
------------------------------------
All PRs merged
https://github.com/jbosstools/jbosstools-base/pull/466
https://github.com/jbosstools/jbosstools-hibernate/pull/82
https://github.com/jbosstools/jbosstools-openshift/pull/816
TP is rebuilt. Everything looks shiny.
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-base_maste... (blue as of the last source change, but yellow now because 2 test failures that passed in the previous build - http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... )
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-hibernate_... (blue!)
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-openshift_... (blue!)
> Create and use Neon M3 target platform (was: Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9)
> --------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-20976
> URL: https://issues.jboss.org/browse/JBIDE-20976
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform, upstream
> Affects Versions: 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 4.4.0.Alpha1
>
> Attachments: features_Mars.0-vs.1.vs.NeonM2.png.png, JBIDE20976_NeonM2.png, JBIDE20976_NeonM2_sapphire.png, p2diff-all.txt, p2diff-summary.txt, p2diff.central.summary.txt, p2diff.central.txt, p2diff.ea.summary.txt, p2diff.ea.txt, p2diff.jbdevstudio_v2.txt, p2diff.jbosstools.txt, plugins_Mars.0-vs.1.vs.NeonM2.png, versionwatch-features.png, versionwatch-plugins.png
>
>
> Opened in JBIDE (not JBDS) because the TPs are essentially the same, so this affects both JBT and JBDS.
> Could be a problem w/ the .target files, or a problem upstream w/ Eclipse projects in Neon not being updated from Mars.0 to their Mars.1 version (or newer).
> Details in these logs:
> http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.vers...
> http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.vers...
> Affected IUs (now sorted alphabetically):
> {code}
> org.eclipse.core.runtime 3.11.1.v20150903-1804
> org.eclipse.egit 4.0.2.201509141540-r
> org.eclipse.egit.core 4.0.2.201509141540-r
> org.eclipse.egit.doc 4.0.2.201509141540-r
> org.eclipse.egit.ui 4.0.2.201509141540-r
> org.eclipse.equinox.p2.rcp.feature 1.2.101.v20150826-1318
> org.eclipse.equinox.p2.user.ui 2.2.101.v20150826-1318
> org.eclipse.jdt 3.11.1.v20150904-0015
> org.eclipse.jdt.doc.user 3.11.1.v20150819-1130
> org.eclipse.jetty.webapp 9.2.13.v20150730
> org.eclipse.jetty.xml 9.2.13.v20150730
> org.eclipse.jgit 4.0.2.201509141540-r
> org.eclipse.jgit.archive 4.0.2.201509141540-r
> org.eclipse.jst.common.frameworks 1.1.701.v201509021802
> org.eclipse.jst.server.tomcat.core 1.1.701.v201508232356
> org.eclipse.jst.web_core.feature 3.7.1.v201509021802
> org.eclipse.jst.web_ui.feature 3.7.1.v201509021802
> org.eclipse.jst.webpageeditor.feature 2.7.1.v201508270443
> org.eclipse.pde 3.11.1.v20150904-0345
> org.eclipse.pde.doc.user 3.11.1.v20150903-1352
> org.eclipse.platform 4.5.1.v20150904-0015
> org.eclipse.platform.doc.user 4.5.1.v20150819-1130
> org.eclipse.rcp 4.5.1.v20150904-0015
> org.eclipse.sapphire 9.0.1.201509151939
> org.eclipse.sapphire.java 9.0.1.201509151939
> org.eclipse.sapphire.java.jdt 9.0.1.201509151939
> org.eclipse.sapphire.java.jdt.ui 9.0.1.201509151939
> org.eclipse.sapphire.modeling 9.0.1.201509151939
> org.eclipse.sapphire.modeling.xml 9.0.1.201509151939
> org.eclipse.sapphire.osgi 9.0.1.201509151939
> org.eclipse.sapphire.osgi.fragment 9.0.1.201509151939
> org.eclipse.sapphire.platform 9.0.1.201509151939
> org.eclipse.sapphire.ui 9.0.1.201509151939
> org.eclipse.sapphire.ui.swt.gef 9.0.1.201509151939
> org.eclipse.sapphire.ui.swt.xml.editor 9.0.1.201509151939
> org.eclipse.sapphire.workspace 9.0.1.201509151939
> org.eclipse.sapphire.workspace.ui 9.0.1.201509151939
> org.eclipse.swt 3.104.1.v20150825-0743
> org.eclipse.wst.common_core.feature 3.7.1.v201508262220
> org.eclipse.wst.common_ui.feature 3.7.1.v201508262220
> org.eclipse.wst.jsdt.feature 1.6.201.v201508262249
> org.eclipse.wst.server.core 1.7.0.v201508271522
> org.eclipse.wst.server.discovery 1.1.0.v201508271522
> org.eclipse.wst.server.ui 1.5.201.v201509022125
> org.eclipse.wst.server_core.feature 3.3.600.v201508271522
> org.eclipse.wst.server_ui.feature 3.3.600.v201509022125
> org.eclipse.wst.validation 1.2.700.v201508251749
> org.eclipse.wst.web_core.feature 3.7.1.v201508271605
> org.eclipse.wst.web_ui.feature 3.7.1.v201509022125
> org.eclipse.wst.ws_ui.feature 3.7.1.v201508271926
> org.eclipse.wst.xml_ui.feature 3.7.1.v201508271605
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBDS-3548) CDK runs Docker 1.7.1 which fails on returning search results
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBDS-3548?page=com.atlassian.jira.plugin.... ]
Xavier Coulon closed JBDS-3548.
-------------------------------
Release Notes Text: CDK2Beta3 ships with Docker 1.8.2 which includes a fix for this problem.
Resolution: Done
> CDK runs Docker 1.7.1 which fails on returning search results
> -------------------------------------------------------------
>
> Key: JBDS-3548
> URL: https://issues.jboss.org/browse/JBDS-3548
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: docker
> Affects Versions: 9.0.0.GA
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Priority: Blocker
> Fix For: 9.1.0.Beta1
>
>
> When searching for an image on DockerHub via a connection to CDK, Eclipse reports this kind of error:
> {code}
> Caused by: org.glassfish.jersey.message.internal.MessageBodyProviderNotFoundException: MessageBodyReader not found for media type=text/plain; charset=utf-8, type=interface java.util.List, genericType=java.util.List<com.spotify.docker.client.messages.ImageSearchResult>.
> at org.glassfish.jersey.message.internal.ReaderInterceptorExecutor$TerminalReaderInterceptor.aroundReadFrom(ReaderInterceptorExecutor.java:230)
> at org.glassfish.jersey.message.internal.ReaderInterceptorExecutor.proceed(ReaderInterceptorExecutor.java:154)
> at org.glassfish.jersey.message.internal.MessageBodyFactory.readFrom(MessageBodyFactory.java:1124)
> {code}
> which is caused by this bug in Docker: https://github.com/docker/docker/pull/14850
> This bug has been fixed in Docker 1.8: https://github.com/docker/docker/commit/5328cc346f56beae2f5a230d445ebdc5b... so the Docker version in CDK needs to be upgraded.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months