[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 reassigned JBDS-3548:
-----------------------------------
Assignee: Xavier Coulon
> 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
[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 updated JBDS-3548:
--------------------------------
Fix Version/s: 9.1.0.Beta1
> 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
[JBoss JIRA] (JBIDE-21012) Why do we deploy JBT components to Nexus snapshots repo?
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21012?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-21012.
------------------------------
Resolution: Done
> Why do we deploy JBT components to Nexus snapshots repo?
> --------------------------------------------------------
>
> Key: JBIDE-21012
> URL: https://issues.jboss.org/browse/JBIDE-21012
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, updatesite
> Affects Versions: 4.3.0.Final, 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
>
> Currently, we deploy our x.y.z-SNAPSHOT update sites to the JBoss Nexus snapshots repo.
> But other than Locus and the Browsersim Standalone zip, we don't ever use these artifacts, so they just:
> * eat disk space in Nexus
> * consume time/resources in Jenkins
> Since we have the custom profile deploy-to-jboss.org in place for all our artifacts, why don't we set *maven.deploy.skip=true* in the parent pom for all the projects (except of course Locus and Browsersim Standalone, which would use maven.deploy.skip=false) ?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21012) Why do we deploy JBT components to Nexus snapshots repo?
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21012?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-21012:
------------------------------------
Parent poms rebuilt. Browsersim rebuilt, but only deployed to dl.jb.org. Browsersim standalone rebuilt and redeployed to Nexus & dl.jb.org (as expected):
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bro...
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-bro...
Also realized we link to the wrong URL in JBT website, so here's a PR for that: https://github.com/jbosstools/jbosstools-website/pull/526 ( JBIDE-18432 )
Rebuilt Locus here:
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... (update.site-1.5.0-20151120.153147-2.zip dated Fri Nov 20 10:31:49 EST 2015)
https://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/lo... (dated Fri Nov 20 10:31:49 EST 2015)
So... locus and browsersim are still deploying correctly after changes.
Also kicked a freemarker build:
http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-fre... shows a build B322 from today, yet Nexus is NOT updated (as expected):
https://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/fr...
https://repository.jboss.org/nexus/content/unzip/unzip/org/jboss/tools/fr... (nothing new since Nov 15)
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... (nothing new since Nov 15)
So... this is verified working for the 2 cases where Nexus deployment should continue, and for 2 cases (of >40) where it should not. I'm not going to test the other 38+ cases since they all use the same parent pom. :D
> Why do we deploy JBT components to Nexus snapshots repo?
> --------------------------------------------------------
>
> Key: JBIDE-21012
> URL: https://issues.jboss.org/browse/JBIDE-21012
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, updatesite
> Affects Versions: 4.3.0.Final, 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
>
> Currently, we deploy our x.y.z-SNAPSHOT update sites to the JBoss Nexus snapshots repo.
> But other than Locus and the Browsersim Standalone zip, we don't ever use these artifacts, so they just:
> * eat disk space in Nexus
> * consume time/resources in Jenkins
> Since we have the custom profile deploy-to-jboss.org in place for all our artifacts, why don't we set *maven.deploy.skip=true* in the parent pom for all the projects (except of course Locus and Browsersim Standalone, which would use maven.deploy.skip=false) ?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-18432) consider refactoring org.jboss.tools.vpe.browsersim_3.6.0 to org.jboss.tools.browsersim_3.7.0
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18432?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-18432:
-------------------------------
Git Pull Request: https://github.com/jbosstools/jbosstools-browsersim/pull/57, https://github.com/jbosstools/jbosstools-build-sites/pull/177, https://github.com/jbdevstudio/jbdevstudio-product/pull/278, https://github.com/jbosstools/jbosstools-discovery/pull/269, https://github.com/jbosstools/jbosstools-website/pull/526 (was: https://github.com/jbosstools/jbosstools-browsersim/pull/57, https://github.com/jbosstools/jbosstools-build-sites/pull/177, https://github.com/jbdevstudio/jbdevstudio-product/pull/278, https://github.com/jbosstools/jbosstools-discovery/pull/269)
> consider refactoring org.jboss.tools.vpe.browsersim_3.6.0 to org.jboss.tools.browsersim_3.7.0
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-18432
> URL: https://issues.jboss.org/browse/JBIDE-18432
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim
> Affects Versions: 4.3.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Konstantin Marmalyukov
> Priority: Minor
> Fix For: 4.3.0.Alpha2, 4.3.1.Beta1, 4.4.0.Alpha1
>
>
> Should we consider refactoring org.jboss.tools.vpe.browsersim_3.6.0 to org.jboss.tools.browsersim_3.7.0, since it's no longer in the VPE project but in the Browsersim project?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21012) Why do we deploy JBT components to Nexus snapshots repo?
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21012?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-21012:
-------------------------------
Git Pull Request: https://github.com/jbosstools/jbosstools-freemarker/pull/54, https://github.com/jbdevstudio/jbdevstudio-ci/pull/156, https://github.com/jbosstools/jbosstools-browsersim/pull/79, https://github.com/jbosstools/jbosstools-browsersim/pull/80 (was: https://github.com/jbosstools/jbosstools-freemarker/pull/54, https://github.com/jbdevstudio/jbdevstudio-ci/pull/156)
PRs to ensure that browsersim standalone continues to deploy-to-jboss.org using maven.deploy.skip = false for 4.3.x and master:
https://github.com/jbosstools/jbosstools-browsersim/pull/79
https://github.com/jbosstools/jbosstools-browsersim/pull/80
Changes to parent pom in 4.3.x and master:
https://github.com/jbosstools/jbosstools-build/commit/81a8daa31917cab5e40...
https://github.com/jbosstools/jbosstools-build/commit/313c2e249d9000e2786...
> Why do we deploy JBT components to Nexus snapshots repo?
> --------------------------------------------------------
>
> Key: JBIDE-21012
> URL: https://issues.jboss.org/browse/JBIDE-21012
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, updatesite
> Affects Versions: 4.3.0.Final, 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
>
> Currently, we deploy our x.y.z-SNAPSHOT update sites to the JBoss Nexus snapshots repo.
> But other than Locus and the Browsersim Standalone zip, we don't ever use these artifacts, so they just:
> * eat disk space in Nexus
> * consume time/resources in Jenkins
> Since we have the custom profile deploy-to-jboss.org in place for all our artifacts, why don't we set *maven.deploy.skip=true* in the parent pom for all the projects (except of course Locus and Browsersim Standalone, which would use maven.deploy.skip=false) ?
--
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 Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20976?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-20976:
------------------------------------------
[~dgolovin] I merged your PR for openshift/master.
> 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] (JBIDE-21082) Application wizard opens when not logged to Openshift
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21082?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21082:
-------------------------------------
Fix Version/s: 4.3.1.Beta1
> Application wizard opens when not logged to Openshift
> -----------------------------------------------------
>
> Key: JBIDE-21082
> URL: https://issues.jboss.org/browse/JBIDE-21082
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Jan Richter
> Labels: application_wizard, openshift_v3
> Fix For: 4.3.1.Beta1
>
>
> Creating new application on a connection where I'm not logged in results in the following:
> First it opens an error dialog (which looks fine):
> {noformat}
> An internal error occurred during: "Loading projects, templates...".
> Could not list Project resources in namespace : javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
> {noformat}
> And then it opens the application wizard anyway.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months