June 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-25504) Support hot deploy for workspace dependencies for SpringBoot applications on OpenShift

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25504?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-25504: ------------------------------------ Here's what I did: * install a brand new Fedora 26 VM * install java-1.8.0-openjdk package * installed DevStudio 12.0.0.AM3 * imported the two projects as Maven projects at once The two projects have the Utility facet but the Deployment Assembly for camel-ose-springboot-xml list penguins 3 times and the warning 'Cannot find entry: penguins' is displayed 3 times as well. !fedora26-screenshot-1.png|thumbnail! > Support hot deploy for workspace dependencies for SpringBoot applications on OpenShift > -------------------------------------------------------------------------------------- > > Key: JBIDE-25504 > URL: https://issues.jboss.org/browse/JBIDE-25504 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.5.2.AM2 > Reporter: Jeff MAURY > Assignee: Andre Dietisheim > Labels: openshift, openshift_v3, server_adapter > Fix For: 4.6.0.AM2 > > Attachments: fedora26-screenshot-1.png, springboot-dependencies.zip > > > When a SpringBoot application is being deployed on OpenShift with the server adapter, we should support the following use case: > * the SpringBoot app has a dependency which is avalailable in the workspace > * when a modifiction is done on the dependency code, it should be synced to OpenShift by the server adapter -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25504) Support hot deploy for workspace dependencies for SpringBoot applications on OpenShift

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25504?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25504: ------------------------------- Attachment: fedora26-screenshot-1.png > Support hot deploy for workspace dependencies for SpringBoot applications on OpenShift > -------------------------------------------------------------------------------------- > > Key: JBIDE-25504 > URL: https://issues.jboss.org/browse/JBIDE-25504 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.5.2.AM2 > Reporter: Jeff MAURY > Assignee: Andre Dietisheim > Labels: openshift, openshift_v3, server_adapter > Fix For: 4.6.0.AM2 > > Attachments: fedora26-screenshot-1.png, springboot-dependencies.zip > > > When a SpringBoot application is being deployed on OpenShift with the server adapter, we should support the following use case: > * the SpringBoot app has a dependency which is avalailable in the workspace > * when a modifiction is done on the dependency code, it should be synced to OpenShift by the server adapter -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-204) Docker Machine lookup does not work on Windows machines [EBZ#494305]

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/ERT-204?page=com.atlassian.jira.plugin.sy... ] Jeff MAURY resolved ERT-204. ---------------------------- Resolution: Done Fixed upstream > Docker Machine lookup does not work on Windows machines [EBZ#494305] > -------------------------------------------------------------------- > > Key: ERT-204 > URL: https://issues.jboss.org/browse/ERT-204 > Project: Eclipse Release Train > Issue Type: Bug > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Xavier Coulon > Labels: 5.0.0, Docker, bzira > Fix For: Oxygen.3 (4.7) > > > When creating Docker connection, the docker-machine mechanism does not work on Window as it seems to find docker-machine and not docker-machine.exe -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26117) New OpenShift Connection Wizard: Parse Login command

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26117?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26117: ------------------------------- Fix Version/s: 4.6.x > New OpenShift Connection Wizard: Parse Login command > ---------------------------------------------------- > > Key: JBIDE-26117 > URL: https://issues.jboss.org/browse/JBIDE-26117 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.6.0.Final > Reporter: Josef Kopriva > Fix For: 4.6.x > > > There could be a button for parsing login command in clipboard. > Steps: > 1. User logins in web browser in OpenShift Console. > 2. User clicks on "Copy Login Command" > 3. In OpenShift tooling there could be button for parse login command from clipboard. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25597) TP: create target platforms based on Eclipse Photon

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25597?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-25597: ------------------------------------ Just spoke to Fred Bricon and we'll be updating m2e and m2e-wtp to 1.9/1.4 in Devstudio 12 (see also RHECLIPSE-44). I plan to move up jgit/egit to fix an installation/remediation issue too (JBDS-4708). Not sure if this will break nodeclipse installation -- will need to check. > TP: create target platforms based on Eclipse Photon > --------------------------------------------------- > > Key: JBIDE-25597 > URL: https://issues.jboss.org/browse/JBIDE-25597 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.5.2.Final > Reporter: Jeff MAURY > Assignee: Nick Boldt > Labels: target-platform > Fix For: 4.6.0.AM3, 4.6.0.Final > > Attachments: base.log > > > In order to start Photon based builds, we need a working Photon based target platform > For sprint 148 / AM1: Photon.0.M6 > For sprint 149 / AM2: Photon.0.M7 > For sprint 150 / AM3: Photon.0.RC3 > For sprint 151 / GA: Photon.0.GA -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25683) [WATCHER] OpenShift New Connection: Automatic copying of token does not work on Fedora

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25683?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-25683: ------------------------------------------ Resolving as DONE. > [WATCHER] OpenShift New Connection: Automatic copying of token does not work on Fedora > -------------------------------------------------------------------------------------- > > Key: JBIDE-25683 > URL: https://issues.jboss.org/browse/JBIDE-25683 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.3.AM1 > Environment: F27 > Red Hat JBoss Developer Studio > Version: 11.3.0.AM1 > Build id: AM1-v20180201-0838-B1971 > Reporter: Josef Kopriva > Assignee: Jeff MAURY > Labels: connection_wizard, upstream > Fix For: 4.6.0.Final > > > Automac copying of token does not work on Fedora, but it does on Win10. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25683) [WATCHER] OpenShift New Connection: Automatic copying of token does not work on Fedora

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25683?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-25683. -------------------------------------- Fix Version/s: 4.6.0.Final (was: 4.6.x) Assignee: Andre Dietisheim (was: Jeff MAURY) Resolution: Done > [WATCHER] OpenShift New Connection: Automatic copying of token does not work on Fedora > -------------------------------------------------------------------------------------- > > Key: JBIDE-25683 > URL: https://issues.jboss.org/browse/JBIDE-25683 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.3.AM1 > Environment: F27 > Red Hat JBoss Developer Studio > Version: 11.3.0.AM1 > Build id: AM1-v20180201-0838-B1971 > Reporter: Josef Kopriva > Assignee: Andre Dietisheim > Labels: connection_wizard, upstream > Fix For: 4.6.0.Final > > > Automac copying of token does not work on Fedora, but it does on Win10. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24217) Explorer: Deployment config is not shown when service is deleted.

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24217?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24217: ------------------------------------- Summary: Explorer: Deployment config is not shown when service is deleted. (was: Deployment config is not shown in OpenshiftExplorer, when service is deleted.) > Explorer: Deployment config is not shown when service is deleted. > ----------------------------------------------------------------- > > Key: JBIDE-24217 > URL: https://issues.jboss.org/browse/JBIDE-24217 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.AM2 > Reporter: Radim Hopp > Assignee: Jeff MAURY > Fix For: 4.6.x > > > When service is deleted (in Openshift Explorer), the whole tree node is removed (even though other resources still exist in openshift). > The Deployment config node is not even shown when "refresh" is used. Only thing that helps is removing whole Openshift connection and adding it back again. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24899) Deploy Docker Image wizard: Image not found

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24899?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-24899: ---------------------------------------- Assignee: (was: Jeff MAURY) > Deploy Docker Image wizard: Image not found > ------------------------------------------- > > Key: JBIDE-24899 > URL: https://issues.jboss.org/browse/JBIDE-24899 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, docker, openshift > Affects Versions: 4.5.1.AM1 > Reporter: Josef Kopriva > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.6.x > > Attachments: image-2017-08-29-09-50-20-927.png > > > Exception in Error log: > {code:java} > Failed to inspect image: '172.30.1.1:5000/test/hola:latest' > com.spotify.docker.client.exceptions.ImageNotFoundException: Image not found: 172.30.1.1:5000/test/hola:latest > at com.spotify.docker.client.DefaultDockerClient.inspectImage(DefaultDockerClient.java:1330) > at org.eclipse.linuxtools.internal.docker.core.DockerConnection.getImageInfo(DockerConnection.java:896) > at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImageWizardModel.lookupImageMetadata(DeployImageWizardModel.java:655) > at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImageWizardModel.initializeContainerInfo(DeployImageWizardModel.java:354) > at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImagePage$1ImageValidatorJob.run(DeployImagePage.java:154) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56) > Caused by: com.spotify.docker.client.exceptions.DockerRequestException: Request error: GET https://192.168.42.121:2376/images/172.30.1.1:5000/test/hola:latest/json: 404 > at com.spotify.docker.client.DefaultDockerClient.propagate(DefaultDockerClient.java:2084) > at com.spotify.docker.client.DefaultDockerClient.request(DefaultDockerClient.java:2023) > at com.spotify.docker.client.DefaultDockerClient.inspectImage(DefaultDockerClient.java:1326) > ... 5 more > Caused by: javax.ws.rs.NotFoundException: HTTP 404 Not Found > at org.glassfish.jersey.client.JerseyInvocation.convertToException(JerseyInvocation.java:1008) > at org.glassfish.jersey.client.JerseyInvocation.translate(JerseyInvocation.java:816) > at org.glassfish.jersey.client.JerseyInvocation.access$700(JerseyInvocation.java:92) > at org.glassfish.jersey.client.JerseyInvocation$5.completed(JerseyInvocation.java:773) > at org.glassfish.jersey.client.ClientRuntime.processResponse(ClientRuntime.java:198) > at org.glassfish.jersey.client.ClientRuntime.access$300(ClientRuntime.java:79) > at org.glassfish.jersey.client.ClientRuntime$2.run(ClientRuntime.java:180) > at org.glassfish.jersey.internal.Errors$1.call(Errors.java:271) > at org.glassfish.jersey.internal.Errors$1.call(Errors.java:267) > at org.glassfish.jersey.internal.Errors.process(Errors.java:315) > at org.glassfish.jersey.internal.Errors.process(Errors.java:297) > at org.glassfish.jersey.internal.Errors.process(Errors.java:267) > at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:340) > at org.glassfish.jersey.client.ClientRuntime$3.run(ClientRuntime.java:210) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > eclipse.buildId=11.1.0.AM1-v20170824-1835-B873 > java.version=1.8.0_141 > java.vendor=Oracle Corporation > BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US > Framework arguments: -product com.jboss.devstudio.core.product > Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23711) Properites: "Edit default route" on Build config does nothing

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23711?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23711: ------------------------------------------ Just reproduce this, it still exists as in 4.6.0.AM3 > Properites: "Edit default route" on Build config does nothing > ------------------------------------------------------------- > > Key: JBIDE-23711 > URL: https://issues.jboss.org/browse/JBIDE-23711 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.AM1 > Reporter: Radim Hopp > Labels: openshift_v3, properties > Fix For: 4.6.x > > > Context menu of build configs in properties view has entry "Edit default route..." which does nothing. Is it even supposed to be there? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 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 2018