July 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22709) Application Wizard: Prompt to create a new project if there is none is not shown

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22709?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-22709. --------------------------------- Verified in devstudio 10.0.1.AM2 AM2-v20160720-1632-B5674. > Application Wizard: Prompt to create a new project if there is none is not shown > -------------------------------------------------------------------------------- > > Key: JBIDE-22709 > URL: https://issues.jboss.org/browse/JBIDE-22709 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Labels: application_wizard, openshift_v3 > Fix For: 4.4.1.AM2 > > > When I have an OpenShift 3 connection without any projects on it, there was a prompt to create a new project (New Project dialog has been opened upon opening of New OpenShift Application wizard). Now when I open a New OpenShift Application Wizard on a connection without any project there is no prompt to create it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22806) Connection wizard: "Finish" is enabled even though I didnt oauth authenticate to pick a token

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22806?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22806: ------------------------------------- Attachment: connection-page-finish-enabled.png > Connection wizard: "Finish" is enabled even though I didnt oauth authenticate to pick a token > --------------------------------------------------------------------------------------------- > > Key: JBIDE-22806 > URL: https://issues.jboss.org/browse/JBIDE-22806 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Andre Dietisheim > Priority: Minor > Fix For: 4.4.1.AM3 > > Attachments: connection-page-finish-enabled.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22806) Connection wizard: "Finish" is enabled even though I didnt oauth authenticate to pick a token

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22806?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22806: ------------------------------------- Priority: Minor (was: Major) > Connection wizard: "Finish" is enabled even though I didnt oauth authenticate to pick a token > --------------------------------------------------------------------------------------------- > > Key: JBIDE-22806 > URL: https://issues.jboss.org/browse/JBIDE-22806 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Andre Dietisheim > Priority: Minor > Fix For: 4.4.1.AM3 > > Attachments: connection-page-finish-enabled.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22806) Connection wizard: "Finish" is enabled even though I didnt oauth authenticate to pick a token

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-22806: ---------------------------------------- Summary: Connection wizard: "Finish" is enabled even though I didnt oauth authenticate to pick a token Key: JBIDE-22806 URL: https://issues.jboss.org/browse/JBIDE-22806 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.4.1.AM2 Reporter: Andre Dietisheim -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22806) Connection wizard: "Finish" is enabled even though I didnt oauth authenticate to pick a token

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22806?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22806: ------------------------------------- Fix Version/s: 4.4.1.AM3 > Connection wizard: "Finish" is enabled even though I didnt oauth authenticate to pick a token > --------------------------------------------------------------------------------------------- > > Key: JBIDE-22806 > URL: https://issues.jboss.org/browse/JBIDE-22806 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Andre Dietisheim > Fix For: 4.4.1.AM3 > > Attachments: connection-page-finish-enabled.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22651) No favicons for credentials domains on Mac or Windows

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22651?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22651: ------------------------------------ [~jeffmaury] I don't understand your comment. If this is fixed, there's nothing blocking us from doing an AM2 release... especially now that Jenkins is working again w/ the new load balancer / DNS. > No favicons for credentials domains on Mac or Windows > ----------------------------------------------------- > > Key: JBIDE-22651 > URL: https://issues.jboss.org/browse/JBIDE-22651 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.4.0.Final > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.4.1.AM2 > > > Supposedly there should be favicons displayed for our jboss.org and redhat.com domains in the credentials preferences: > Preferences -> JBoss Tools -> Credentials > I only noticed this problem after reviewing JBIDE-22468 . And [~jkopriva] just showed me on his Linux box that he has the icons there. I don't have any icons on Mac or Windows. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22639) Server Adapter Editor: Opening an Openshift3 server adapter when connection does not exists anymore causes NPE

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22639?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-22639. --------------------------------- Verified in devstudio 10.0.1.AM2 AM2-v20160720-1632-B5674. > Server Adapter Editor: Opening an Openshift3 server adapter when connection does not exists anymore causes NPE > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22639 > URL: https://issues.jboss.org/browse/JBIDE-22639 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, server > Affects Versions: 4.4.0.Final > Reporter: Jeff MAURY > Assignee: Andre Dietisheim > Labels: server_adapter_editor > Fix For: 4.4.1.AM2 > > Attachments: non-existent-workspace-reference.png, screenshot-1.png > > > ASSERT: create an Openshift3 connection > ASSERT: create a server adapter from that connection > ASSERT: delete the Openshift3 connection > EXEC: open the server adapter > ASSERT: NPE is thrown and dialog is displayed (see [^screenshot-1.png]) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22686) Can't push image to docker registry

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22686?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-22686. --------------------------------- Closed as cannot reproduce. > Can't push image to docker registry > ----------------------------------- > > Key: JBIDE-22686 > URL: https://issues.jboss.org/browse/JBIDE-22686 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker, openshift > Affects Versions: 4.4.0.Final > Environment: Fedora 23 > Reporter: Dmitry Bocharov > Assignee: Dmitry Bocharov > Fix For: 4.4.1.AM2 > > Attachments: DeployDockerImageToOS.webm, DeployedSuccessfully.webm > > > The screencast of the last steps is attached. > Properties and settings of the cdk haven't been changed. Everything is dowloaded and installed in a usual way. > Possibly something is with the dns - maybe it wasn't configured correctly while cdk installation. Because we to push to the valid url, while OS connection only an IP in its settings. > _exception:_ > org.eclipse.linuxtools.docker.core.DockerException: com.spotify.docker.client.DockerException: org.eclipse.linuxtools.docker.core.DockerImagePushFailedException: Image push failed: hub.openshift.rhel-cdk.10.1.2.2.xip.io/sample-project/aloha: unable to ping registry endpoint https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v0/ > v2 ping attempt failed with error: Get https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v2/: dial tcp 10.1.2.2:443: connection refused > v1 ping attempt failed with error: Get https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v1/_ping: dial tcp 10.1.2.2:443: connection refused > at org.eclipse.linuxtools.internal.docker.core.DockerConnection.pushImage(DockerConnection.java:1047) > at org.jboss.tools.openshift.internal.ui.dockerutils.PushImageToRegistryJob.doRun(PushImageToRegistryJob.java:67) > at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:37) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Caused by: com.spotify.docker.client.DockerException: org.eclipse.linuxtools.docker.core.DockerImagePushFailedException: Image push failed: hub.openshift.rhel-cdk.10.1.2.2.xip.io/sample-project/aloha: unable to ping registry endpoint https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v0/ > v2 ping attempt failed with error: Get https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v2/: dial tcp 10.1.2.2:443: connection refused > v1 ping attempt failed with error: Get https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v1/_ping: dial tcp 10.1.2.2:443: connection refused > at org.eclipse.linuxtools.internal.docker.core.DockerProgressHandler.progress(DockerProgressHandler.java:42) > at com.spotify.docker.client.ProgressStream.tail(ProgressStream.java:74) > at com.spotify.docker.client.DefaultDockerClient.push(DefaultDockerClient.java:821) > at org.eclipse.linuxtools.internal.docker.core.DockerConnection.pushImage(DockerConnection.java:1043) > ... 3 more > Caused by: org.eclipse.linuxtools.docker.core.DockerImagePushFailedException: Image push failed: hub.openshift.rhel-cdk.10.1.2.2.xip.io/sample-project/aloha: unable to ping registry endpoint https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v0/ > v2 ping attempt failed with error: Get https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v2/: dial tcp 10.1.2.2:443: connection refused > v1 ping attempt failed with error: Get https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v1/_ping: dial tcp 10.1.2.2:443: connection refused > at org.eclipse.linuxtools.internal.docker.ui.views.ImagePushProgressHandler.processMessage(ImagePushProgressHandler.java:49) > at org.eclipse.linuxtools.internal.docker.core.DockerProgressHandler.progress(DockerProgressHandler.java:40) > ... 6 more -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22764) OpenShift 3 doesn't compile with latest changes in Docker tooling

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22764?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-22764. --------------------------------- > OpenShift 3 doesn't compile with latest changes in Docker tooling > ------------------------------------------------------------------ > > Key: JBIDE-22764 > URL: https://issues.jboss.org/browse/JBIDE-22764 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.4.1.AM2 > > > Some temporary hack (https://github.com/jbosstools/jbosstools-openshift/commit/189fd3dfc006086...) no longer compiles against the latest docker tooling (in master) code: > {code:java} > // FIXME: needs to catch DockerCertificateException until > // https://bugs.eclipse.org/bugs/show_bug.cgi?id=495249 is fixed > catch (DockerException | InterruptedException | DockerCertificateException e) { > return new Status(IStatus.ERROR, OpenShiftUIActivator.PLUGIN_ID, > "Failed to push the selected Docker image into OpenShift registry", e); > } > {code} > com.spotify.docker.client.DockerCertificateException is no longer thrown by the Docker API so the catch block fails to compile. > We can fix the compilation problem with Neon.1 while still maintaining Neon.0 compatibility with a different, yet fugly, trick. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22632) Spurious message due to incorrect I18N

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22632?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-22632. --------------------------------- Verified in devstudio 10.0.1.AM2 AM2-v20160720-1632-B5674. > Spurious message due to incorrect I18N > -------------------------------------- > > Key: JBIDE-22632 > URL: https://issues.jboss.org/browse/JBIDE-22632 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Minor > Fix For: 4.4.1.AM2 > > > When JBossTools Openshift is starting, a spurious message is written in the Eclipse log:{{ > Warning: NLS missing message: ProjectDeletionDialogTitle in: org.jboss.tools.openshift.internal.ui.OpenShiftUIMessages}} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 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 July 2016