April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21885) Remove "()" from context-menu name of Start Build

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21885?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-21885: ---------------------------------------- Assignee: Andre Dietisheim > Remove "()" from context-menu name of Start Build > -------------------------------------------------- > > Key: JBIDE-21885 > URL: https://issues.jboss.org/browse/JBIDE-21885 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Environment: JBoss OpenShift 3 Tools 3.2.0.Alpha1-v20160316-2139-B1202 > OS: Fedora 22 & Windows 10 > Reporter: Xia Zhao > Assignee: Andre Dietisheim > Priority: Minor > Labels: openshift_v3 > Fix For: 4.4.0.Alpha1 > > Attachments: build-config-properties-menu.png > > > The "()" from context-menu name of Start Build should be removed -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21861) Include Docker tooling 2.0.0 in JBT 4.4.x TP

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21861?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-21861: --------------------------------------------- I have not tried latest vagrant tooling so can't say. Something you need resolving between OpenShift, Docker and CDK components what makes sense to do. > Include Docker tooling 2.0.0 in JBT 4.4.x TP > -------------------------------------------- > > Key: JBIDE-21861 > URL: https://issues.jboss.org/browse/JBIDE-21861 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.3.1.Beta2 > Reporter: Xavier Coulon > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha2 > > > Include Docker tooling 2.0.0 in Target Platform 4.60.x, targeting JBoss Tools 4.4.x -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22051) Redesing route prompting in server adapter wizard, show in browser etc.

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22051?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22051: ------------------------------------- Fix Version/s: 4.4.x (was: 4.4.0.Alpha1) > Redesing route prompting in server adapter wizard, show in browser etc. > ----------------------------------------------------------------------- > > Key: JBIDE-22051 > URL: https://issues.jboss.org/browse/JBIDE-22051 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Andre Dietisheim > Labels: openshift_v3, server_adapter, server_adapter_wizard > Fix For: 4.4.x > > > We currently allow the user NOT to choose a route for a server adapter. This might result in an adapter without proper host (since the host is derived from the route). In 4.3.1 we worked around it by always using the 1st available route as host, even though we possibly prompt the user and let it choose the route when he does Show In > Browser. > According to [~rob.stryker] WTP adapters are designed to sit on a proper host. We should follow this pattern and use available WTP API to still allow the user to use different routes with an adapter. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22079) Import wizard: Error when import a project already existing in workspace

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22079?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22079: ------------------------------------- Fix Version/s: 4.4.0.Alpha2 (was: 4.4.0.Alpha1) > Import wizard: Error when import a project already existing in workspace > ------------------------------------------------------------------------ > > Key: JBIDE-22079 > URL: https://issues.jboss.org/browse/JBIDE-22079 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Labels: import_wizard, openshift_v3 > Fix For: 4.4.0.Alpha2 > > Attachments: import-error.png > > > When I am creating a new OpenShift application using an existing repo, or at least project in workspace, it throws an error upon application creation completion. This is a bit of pain, because even I have an existing git repo and checked the checkbox in Import Wizard to reuse it, it tries to import project then, but it fails. But the existing project is still usable to use it for a new OpenShift 3 server adapter and upon start of the adapter, local changes are published to OpenShift. This issue is just about error. Maybe we could display a dialog that such a project already exists in workspace and let user to choose to replace it by the one being imported or keep it as it is (if user know that the project in workspace is the correct one and he/she does not want to overwrite it and let local changes disappear). > Error: > {code}Could not import project from org.jboss.tools.openshift.internal.common.ui.application.importoperation.ImportFailedException: There was a maven related error that prevented us from importing the project. We encourage you to look into the pom in the cloned repository at /home/mlabuda/git/jboss-eap-quickstarts. > One of the possible reasons is that there is already a project in your workspace that matches the maven name of the OpenShift application. You can then rename your workspace project and start over again. > An exception stack trace is not available. > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22165) Deploy Docker wizard: Check "Add Route" checkbox for exposing services of docker image by default

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22165?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22165: ------------------------------------- Fix Version/s: 4.4.x (was: 4.4.0.Alpha1) > Deploy Docker wizard: Check "Add Route" checkbox for exposing services of docker image by default > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-22165 > URL: https://issues.jboss.org/browse/JBIDE-22165 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Labels: deploy_docker_wizard, docker, openshift_v3 > Fix For: 4.4.x > > > I think usually users would like to expose their services of a docker image being deployed to OpenShift. In the Deploy Image to OpenShift wizard we have a wizard page where mapping of ports is happening and also exposing of services to routes by checking a checkbox "Add Route" is placed there. By default we have this checkbox unchecked, but maybe we should enable it by default. In my humble opinion in many use case there will be an existing docker image of some application and user would like to deploy it to OpenShift and check application whether it is working or use some features of OpenShift itself... > At the moment we don't have enabled exposing of OpenShift resources in tooling and therefore if user by accident or intentionally click on Finish button in Deploy Image to OpenShift wizard one page earlier (the one where env. vars, scaling and data volumes are located), it produce a running pod with service, but there is no route and it force user to swich to command line to use oc to expose a service to get a route. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19506) Connection wizard: should have unit tests

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19506?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19506: ------------------------------------- Fix Version/s: 4.4.0.Alpha2 (was: 4.4.0.Alpha1) > Connection wizard: should have unit tests > ------------------------------------------ > > Key: JBIDE-19506 > URL: https://issues.jboss.org/browse/JBIDE-19506 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openshift_v3, tests > Fix For: 4.4.0.Alpha2 > > > In the new implementation of the connection wizard, that allows v2 and v3 connections (JBIDE-19096) we have rather complex behaviour that we should assert via unit tests. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21731) Server Adapter: Error shown when image is not created/pushed yet, should be more user friendly

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21731?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21731: ------------------------------------- Fix Version/s: 4.4.0.Alpha2 (was: 4.4.0.Alpha1) > Server Adapter: Error shown when image is not created/pushed yet, should be more user friendly > ---------------------------------------------------------------------------------------------- > > Key: JBIDE-21731 > URL: https://issues.jboss.org/browse/JBIDE-21731 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.4.0.Alpha2 > > Attachments: cannot_get_image.png > > > When I create a new OS3 application and then I want to create a new server adapter, an image for this application has to be built and pushed to OpenShift's local image registry. If build is still running, what is often happening on internal OSE instance (it takes minutes - pushing of images), then there is an error message that loading of image failed. User without solid overview of OS3 background would not be able to figure out why it is happening, because even Image stream is shown, but the image is not there yet. > Full error log: > {code} > com.openshift.restclient.OpenShiftException: Could not get resource django-example:latest in namespace image: { > "kind": "Status", > "apiVersion": "v1", > "metadata": {}, > "status": "Failure", > "message": "imageStreamTag \"django-example:latest\" not found", > "reason": "NotFound", > "details": { > "name": "django-example:latest", > "kind": "imageStreamTag" > }, > "code": 404 > } > at com.openshift.internal.restclient.DefaultClient.createOpenShiftException(DefaultClient.java:481) > at com.openshift.internal.restclient.DefaultClient.get(DefaultClient.java:306) > at org.jboss.tools.openshift.core.connection.Connection.getResource(Connection.java:378) > at org.jboss.tools.openshift.internal.ui.models.DeploymentResourceMapper.lambda$5(DeploymentResourceMapper.java:106) > at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193) > at java.util.HashMap$KeySpliterator.forEachRemaining(HashMap.java:1540) > at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481) > at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471) > at java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:708) > at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) > at java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:499) > at org.jboss.tools.openshift.internal.ui.models.DeploymentResourceMapper.getImageStreamTagsFor(DeploymentResourceMapper.java:107) > at org.jboss.tools.openshift.internal.ui.models.DeploymentResourceMapper.lambda$2(DeploymentResourceMapper.java:87) > at java.util.stream.Collectors.lambda$toMap$213(Collectors.java:1321) > at java.util.stream.ReduceOps$3ReducingSink.accept(ReduceOps.java:169) > at java.util.HashMap$KeySpliterator.forEachRemaining(HashMap.java:1540) > at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481) > at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471) > at java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:708) > at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) > at java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:499) > at org.jboss.tools.openshift.internal.ui.models.DeploymentResourceMapper.getAllImageStreamTags(DeploymentResourceMapper.java:85) > at org.jboss.tools.openshift.internal.ui.server.ServerSettingsViewModel$ProjectImageStreamTags.createImageStreamsMap(ServerSettingsViewModel.java:334) > at org.jboss.tools.openshift.internal.ui.server.ServerSettingsViewModel$ProjectImageStreamTags.<init>(ServerSettingsViewModel.java:327) > at org.jboss.tools.openshift.internal.ui.server.ServerSettingsViewModel.lambda$1(ServerSettingsViewModel.java:279) > at java.util.stream.Collectors.lambda$toMap$213(Collectors.java:1321) > at java.util.stream.ReduceOps$3ReducingSink.accept(ReduceOps.java:169) > at java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1374) > at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481) > at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471) > at java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:708) > at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) > at java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:499) > at org.jboss.tools.openshift.internal.ui.server.ServerSettingsViewModel.createImageStreamTagsMap(ServerSettingsViewModel.java:277) > at org.jboss.tools.openshift.internal.ui.server.ServerSettingsViewModel.loadResources(ServerSettingsViewModel.java:261) > at org.jboss.tools.openshift.internal.ui.server.ServerSettingsViewModel.loadResources(ServerSettingsViewModel.java:255) > at org.jboss.tools.openshift.internal.ui.server.ServerSettingsWizardFragment$15.run(ServerSettingsWizardFragment.java:695) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Caused by: com.openshift.internal.restclient.http.NotFoundException: { > "kind": "Status", > "apiVersion": "v1", > "metadata": {}, > "status": "Failure", > "message": "imageStreamTag \"django-example:latest\" not found", > "reason": "NotFound", > "details": { > "name": "django-example:latest", > "kind": "imageStreamTag" > }, > "code": 404 > } > at com.openshift.internal.restclient.http.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:230) > at com.openshift.internal.restclient.http.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:165) > at com.openshift.internal.restclient.http.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:141) > at com.openshift.internal.restclient.http.UrlConnectionHttpClient.get(UrlConnectionHttpClient.java:103) > at com.openshift.internal.restclient.DefaultClient.get(DefaultClient.java:302) > ... 36 more > Caused by: java.io.FileNotFoundException: https://console.engint.openshift.com/oapi/v1/namespaces/image/imagestream... > at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1836) > at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1441) > at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254) > at com.openshift.internal.restclient.http.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:161) > ... 39 more > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21967) Cannot create server adapter if there is a running build on a project although there are more projects

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21967?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21967: ------------------------------------- Fix Version/s: 4.4.0.Alpha2 (was: 4.4.0.Alpha1) > Cannot create server adapter if there is a running build on a project although there are more projects > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-21967 > URL: https://issues.jboss.org/browse/JBIDE-21967 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.4.0.Alpha2 > > > When I am having several projects and some of them has already running application, I am not able to create a new server adapter for OpenShift 3 application if there is a project with running build. Once build finish, it is possible to create a project but while there is any project with not completed build (and therefore application image is not there yet) user is blocked from creating a new server adapter. This is related to JBIDE-21731 - once this issue will be fixed, it should keep in mind to allow users proceed with creation of server adapters on other projects. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22259) Server Adapter: Debugging of OS 3 application creates a new replication controller

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22259?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22259: ------------------------------------- Fix Version/s: 4.4.x (was: 4.4.0.Alpha1) > Server Adapter: Debugging of OS 3 application creates a new replication controller > ---------------------------------------------------------------------------------- > > Key: JBIDE-22259 > URL: https://issues.jboss.org/browse/JBIDE-22259 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Labels: openshift_v3, server_adapter > Fix For: 4.4.x > > > Restart in debug on OS 3 server adapter of eap 6.4 application and related workspace project creates a new replication controller. Every time server is stopped and started, new replication controller is created (although server has been stopped and then started) and a this new replication controller is still debugging (has set debug port). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22265) Application wizard: Allow users to reset values of all template parameters

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22265?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich reassigned JBIDE-22265: --------------------------------------------- Assignee: Viacheslav Kabanovich > Application wizard: Allow users to reset values of all template parameters > -------------------------------------------------------------------------- > > Key: JBIDE-22265 > URL: https://issues.jboss.org/browse/JBIDE-22265 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Priority: Minor > Labels: application_wizard, openshift_v3 > Fix For: 4.4.x > > > At the moment we allow users to reset a specific value in the table containing template parameters in New OpenShift Application wizard. It would be nice to have option to reset all template parameters (get default values for all) to have it consistent across wizards. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 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 April 2016