June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-784) Include New SAP Tooling and SAP Data Layer for Mars branch

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBTIS-784?page=com.atlassian.jira.plugin.... ] Aurélien Pupier resolved JBTIS-784. ----------------------------------- Resolution: Won't Do handled in a different way > Include New SAP Tooling and SAP Data Layer for Mars branch > ---------------------------------------------------------- > > Key: JBTIS-784 > URL: https://issues.jboss.org/browse/JBTIS-784 > Project: JBoss Tools Integration Stack > Issue Type: Component Upgrade > Components: distribution, Fuse IDE > Reporter: Aurélien Pupier > Assignee: Paul Leacu > > I don't know how to process exactly. > Do I modify the URl here? https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/j... > There is currently no new Tag. > We need to pick the 6.3.0-SNAPSHOT for SAP Data Layer from this update site: http://fuse-sap.mw.lab.eng.bos.redhat.com/repositories/fuse-sap-data-laye... > The SAP Tooling should be retrieved from http://download.jboss.org/jbosstools/mars/integration/updates/integration... > Where do I need to modify something to be able to test it? > When teher will be a release, I will need to update again the file? or there some automatic mechanism possible? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-231) Registry accounts does not accept data with _ [EBZ#495072]

by Roland Grunberg (JIRA)

[ https://issues.jboss.org/browse/ERT-231?page=com.atlassian.jira.plugin.sy... ] Roland Grunberg closed ERT-231. ------------------------------- Fix Version/s: Neon (4.6) Assignee: Roland Grunberg Resolution: Done Fixed For Neon. See corresponding Eclipse Bug for information. > Registry accounts does not accept data with _ [EBZ#495072] > ---------------------------------------------------------- > > Key: ERT-231 > URL: https://issues.jboss.org/browse/ERT-231 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Roland Grunberg > Labels: Docker, bzira > Fix For: Neon (4.6) > > > If you configure a docker registry account with hostname=hub_1.docker.com user=a email=b(a)b.com password=c then close the preference dialog and reopen it, then address is now hub, username 1.docker.com and email a. > If you configure a docker registry account with hostname=hub.docker.com user=a_1 email=b(a)b.com password=c then close the preference dialog and reopen it, then address is now hub.docker.com, username a and email 1. > If you configure a docker registry account with hostname=hub.docker.com user=a email=b_1(a)b.com password=c then close the preference dialog and reopen it, then address is now hub.docker.com, username a and email b. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-233) Dialog for adding a new Docker registry account has no title [EBZ#495074]

by Roland Grunberg (JIRA)

[ https://issues.jboss.org/browse/ERT-233?page=com.atlassian.jira.plugin.sy... ] Roland Grunberg closed ERT-233. ------------------------------- Fix Version/s: Neon (4.6) Assignee: Roland Grunberg Resolution: Done Fixed For Neon. See corresponding Eclipse Bug for information. > Dialog for adding a new Docker registry account has no title [EBZ#495074] > ------------------------------------------------------------------------- > > Key: ERT-233 > URL: https://issues.jboss.org/browse/ERT-233 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Roland Grunberg > Labels: Docker, bzira > Fix For: Neon (4.6) > > > Not sure this is compliant with Eclipse UI guidelines -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-238) Issue in DockerConnection#hasImage(String, String) [EBZ#495243]

by Roland Grunberg (JIRA)

[ https://issues.jboss.org/browse/ERT-238?page=com.atlassian.jira.plugin.sy... ] Roland Grunberg updated ERT-238: -------------------------------- Sprint: devex #116 June 2016 > Issue in DockerConnection#hasImage(String,String) [EBZ#495243] > -------------------------------------------------------------- > > Key: ERT-238 > URL: https://issues.jboss.org/browse/ERT-238 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Labels: Docker, bzira > > The method only inspects the first 'repo' value for a given image, so if a given Docker image was tagged with different names (eg: 'jboss/wildfly' and 'xcoulon/wildfly'), then one method call will respond 'false' while it should be 'true'. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-239) PushImageCommandHandler directly references a Spotify client exception [EBZ#495249]

by Roland Grunberg (JIRA)

[ https://issues.jboss.org/browse/ERT-239?page=com.atlassian.jira.plugin.sy... ] Roland Grunberg updated ERT-239: -------------------------------- Sprint: devex #116 June 2016 > PushImageCommandHandler directly references a Spotify client exception [EBZ#495249] > ----------------------------------------------------------------------------------- > > Key: ERT-239 > URL: https://issues.jboss.org/browse/ERT-239 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Labels: Docker, bzira > > I think that this should not happen: the Spotify exceptions should be wrapped by the DockerConnection class and not exposed in the API. > The root cause seems to be in DockerConnection: > public void pushImage(final String name, final IRegistryAccount info, final IDockerProgressHandler handler) > throws DockerException, InterruptedException, DockerCertificateException -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-249) Add Registry Account UI improvement [EBZ#495693]

by Roland Grunberg (JIRA)

[ https://issues.jboss.org/browse/ERT-249?page=com.atlassian.jira.plugin.sy... ] Roland Grunberg updated ERT-249: -------------------------------- Sprint: devex #116 June 2016 > Add Registry Account UI improvement [EBZ#495693] > ------------------------------------------------ > > Key: ERT-249 > URL: https://issues.jboss.org/browse/ERT-249 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Labels: Docker, bzira > > I suggest to add note/change labels in dialog Preferences->Docker->Registry Accounts-> Add . > In Server Address could be just username on Docker Hub or address of the OpenShift Docker Registry - this should be mentioned at least as a note or as a tooltip. > This dialog could be also wider(if server address longer...). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-249) Add Registry Account UI improvement [EBZ#495693]

by Roland Grunberg (JIRA)

[ https://issues.jboss.org/browse/ERT-249?page=com.atlassian.jira.plugin.sy... ] Roland Grunberg reassigned ERT-249: ----------------------------------- Assignee: Roland Grunberg > Add Registry Account UI improvement [EBZ#495693] > ------------------------------------------------ > > Key: ERT-249 > URL: https://issues.jboss.org/browse/ERT-249 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Roland Grunberg > Labels: Docker, bzira > > I suggest to add note/change labels in dialog Preferences->Docker->Registry Accounts-> Add . > In Server Address could be just username on Docker Hub or address of the OpenShift Docker Registry - this should be mentioned at least as a note or as a tooltip. > This dialog could be also wider(if server address longer...). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-250) Cannot deploy image from local repository to remote registry [EBZ#495793]

by Roland Grunberg (JIRA)

[ https://issues.jboss.org/browse/ERT-250?page=com.atlassian.jira.plugin.sy... ] Roland Grunberg reassigned ERT-250: ----------------------------------- Assignee: Roland Grunberg > Cannot deploy image from local repository to remote registry [EBZ#495793] > ------------------------------------------------------------------------- > > Key: ERT-250 > URL: https://issues.jboss.org/browse/ERT-250 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Roland Grunberg > Priority: Critical > Labels: Docker, bzira > > I have a docker connection to local host and a remote registry account in Registry Accounts preference page. For better understanding there is my setup: > - docker host running on local machine (socket at /var/run/docker.sock) > - registry at hub.openshift.rhel-cdk.10.1.2.2.xip.io > - copied registry certificate to local machine to folder /etc/docker/certs.d/hub.openshift.rhel-cdk.10.1.2.2.xip.io/ca.crt (this is necessary because it is docker registry with self-signed certificate and not running with --insecure-registry) > - any local docker image (build locally, not presented on docker hub) > When I am working from command line I do following: > - log in to docker registry hub.openshift.rhel-cdk.10.1.2.2.xip.io with credentials (certificate of docker registry must be present on local machine) > - tag a docker image as follows hub.openshift.rhel-cdk.10.1.2.2.xip.io/mlabuda/aloha > - push the tagged image to registry > When I am working from IDE with docker tools, I select context menu item Push in the context menu of a docker image and select the registry. At first it is trying to push layers to registry but in the end I get following error without any stack trace > "com.spotify.docker.client.DockerException: > org.eclipse.linuxtools.docker.core.DockerImagePushFailedException: Image push failed: hub.openshift.rhel-cdk.10.1.2.2.xip.io/mlabuda/aloha:latest: unknown: request access to the resource is denied". > With docker client from command line everything works ok. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-250) Cannot deploy image from local repository to remote registry [EBZ#495793]

by Roland Grunberg (JIRA)

[ https://issues.jboss.org/browse/ERT-250?page=com.atlassian.jira.plugin.sy... ] Roland Grunberg updated ERT-250: -------------------------------- Sprint: devex #116 June 2016 > Cannot deploy image from local repository to remote registry [EBZ#495793] > ------------------------------------------------------------------------- > > Key: ERT-250 > URL: https://issues.jboss.org/browse/ERT-250 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Priority: Critical > Labels: Docker, bzira > > I have a docker connection to local host and a remote registry account in Registry Accounts preference page. For better understanding there is my setup: > - docker host running on local machine (socket at /var/run/docker.sock) > - registry at hub.openshift.rhel-cdk.10.1.2.2.xip.io > - copied registry certificate to local machine to folder /etc/docker/certs.d/hub.openshift.rhel-cdk.10.1.2.2.xip.io/ca.crt (this is necessary because it is docker registry with self-signed certificate and not running with --insecure-registry) > - any local docker image (build locally, not presented on docker hub) > When I am working from command line I do following: > - log in to docker registry hub.openshift.rhel-cdk.10.1.2.2.xip.io with credentials (certificate of docker registry must be present on local machine) > - tag a docker image as follows hub.openshift.rhel-cdk.10.1.2.2.xip.io/mlabuda/aloha > - push the tagged image to registry > When I am working from IDE with docker tools, I select context menu item Push in the context menu of a docker image and select the registry. At first it is trying to push layers to registry but in the end I get following error without any stack trace > "com.spotify.docker.client.DockerException: > org.eclipse.linuxtools.docker.core.DockerImagePushFailedException: Image push failed: hub.openshift.rhel-cdk.10.1.2.2.xip.io/mlabuda/aloha:latest: unknown: request access to the resource is denied". > With docker client from command line everything works ok. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22612) Explorer: OpenShift connections are missing from the explorer on startup

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22612?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22612: ------------------------------------- Workaround Description: launch OpenShift Connection wizard. As soon as the wizard shows up the v3 connections are listed. V2 connections are still missing. (was: launch OpenShift Connection wizard. As soon as the wizard shows up the connections are listed.) > Explorer: OpenShift connections are missing from the explorer on startup > ------------------------------------------------------------------------ > > Key: JBIDE-22612 > URL: https://issues.jboss.org/browse/JBIDE-22612 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.Alpha1 > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Labels: explorer, openshift_v2, openshift_v3 > Fix For: 4.4.1.Alpha1 > > > After applying the fix for JBIDE-21828, it appears that, on workspace restart, the OpenShift 3 connections are missing from the OpenShift Explorer. > This is caused by the OpenShift 3 core plugin not being started when the OpenShiftExplorerContentProvider is called. As a consequence, no connections are loaded. > Before JBIDE-21828, [getExplorerElements|https://github.com/jbosstools/jbosstools-openshift/co...] would return all the OpenShift3 connections. With the new code, the UI Model is expected to be already loaded -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues June 2016