March 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3633) Uninstaller does nothing

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3633?page=com.atlassian.jira.plugin.... ] Denis Golovin reassigned JBDS-3633: ----------------------------------- Assignee: Denis Golovin > Uninstaller does nothing > ------------------------ > > Key: JBDS-3633 > URL: https://issues.jboss.org/browse/JBDS-3633 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Reporter: Denis Golovin > Assignee: Denis Golovin > Labels: havoc > Fix For: 9.1.0.CR1 > > > Current implementation just removes record about installation fro windows registry -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

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

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21731?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-21731: ------------------------------------------ [~jcantrill] your ability to retrieve the image metadata in https://github.com/openshift/openshift-restclient-java/pull/118, is that what we should use instead of the current implementation via DeploymentResourceMapper? Are there limitations? [~scabanovich][~fbricon] I believe that your suggestions are good (if I understood everything correctly). But I am wondering if we really should load everything upfront: it takes up to 30 seconds and more to load larger/complex project strcutures (see http://screencast.com/t/jweIzStNk - https://github.com/jbosstools/jbosstools-openshift/pull/978). We could either not load the tags at all, simply offer a checkbox to let the adapter derive the deployment forlder and a text-field to manually provide it. The text field would be disabled if the user chooses to let the adapter automatically detect the deployment folder. {code} [x] Detect deployment folder Deployment folder: [ ] {code} Alternatively we could proceed as you suggested, trying to load the tags, but then load them only when the user selects a service in the table. We would then have the progress bar progressing and all the widgets disabled while we're loading from the server. When loaded we could cache the value so that we would not annoy the user a 2nd time. Thoughts? > Server Adapter: Error shown when image is not created/pushed yet, sould 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 > Labels: openshift_v3, server_adapter > Fix For: 4.3.1.CR1 > > 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)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3634) Installer - Add a Finish/Close button to the final screen of the installer

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3634?page=com.atlassian.jira.plugin.... ] Denis Golovin reassigned JBDS-3634: ----------------------------------- Assignee: Joshua Wilson (was: Denis Golovin) > Installer - Add a Finish/Close button to the final screen of the installer > -------------------------------------------------------------------------- > > Key: JBDS-3634 > URL: https://issues.jboss.org/browse/JBDS-3634 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Reporter: Len DiMaggio > Assignee: Joshua Wilson > Labels: havoc, ui > Fix For: 9.1.0.CR1 > > > In the current version of the installer, after a successful installation the user exits the installer by closing the installer window. It would be more "polished" if we added a close button in the UI. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3635) Add the ability to detect/select existing dependencies/tools

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3635?page=com.atlassian.jira.plugin.... ] Denis Golovin reassigned JBDS-3635: ----------------------------------- Assignee: Joshua Wilson (was: Denis Golovin) > Add the ability to detect/select existing dependencies/tools > ------------------------------------------------------------ > > Key: JBDS-3635 > URL: https://issues.jboss.org/browse/JBDS-3635 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Reporter: Jan Richter > Assignee: Joshua Wilson > Labels: havoc, ui > Attachments: pdkinstaller.png > > > It would be great if the installer allowed the user to use some of the required tools they have already installed. > The idea is to detect if the dependencies are already present and let the user decide if they want to use them, or install new ones. Also, it could let the user select the tools themselves if they want to use a different installation than detected, etc. > The confirmation page we currently have looks like the place to put all this, since it already displays most of the stuff that is going to get installed. Anyway, I have tried to modify it and squeeze the controls in and this is how the selection turned out (imagine the messages looking a bit smarter): > !pdkinstaller.png|thumbnail! > [~dgolovin] & [~crobson], what's your opinion on this? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3635) Add the ability to detect/select existing dependencies/tools

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3635?page=com.atlassian.jira.plugin.... ] Denis Golovin reassigned JBDS-3635: ----------------------------------- Assignee: Denis Golovin (was: Joshua Wilson) > Add the ability to detect/select existing dependencies/tools > ------------------------------------------------------------ > > Key: JBDS-3635 > URL: https://issues.jboss.org/browse/JBDS-3635 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Reporter: Jan Richter > Assignee: Denis Golovin > Labels: havoc, ui > Attachments: pdkinstaller.png > > > It would be great if the installer allowed the user to use some of the required tools they have already installed. > The idea is to detect if the dependencies are already present and let the user decide if they want to use them, or install new ones. Also, it could let the user select the tools themselves if they want to use a different installation than detected, etc. > The confirmation page we currently have looks like the place to put all this, since it already displays most of the stuff that is going to get installed. Anyway, I have tried to modify it and squeeze the controls in and this is how the selection turned out (imagine the messages looking a bit smarter): > !pdkinstaller.png|thumbnail! > [~dgolovin] & [~crobson], what's your opinion on this? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3636) Installer - If the installation encounters a box download issue, the install fails, and the user must manually cleanup before retrying

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3636?page=com.atlassian.jira.plugin.... ] Denis Golovin reassigned JBDS-3636: ----------------------------------- Assignee: Joshua Wilson (was: Denis Golovin) > Installer - If the installation encounters a box download issue, the install fails, and the user must manually cleanup before retrying > -------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3636 > URL: https://issues.jboss.org/browse/JBDS-3636 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Reporter: Len DiMaggio > Assignee: Joshua Wilson > Labels: havoc, ui > Attachments: Download.png > > > See the attached screenshot - The installation in question failed due to a download issue with the box file. Only path forward for the user was to manually abort the install, manually cleanup the install, and retry. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3635) Add the ability to detect/select existing dependencies/tools

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3635?page=com.atlassian.jira.plugin.... ] Denis Golovin reassigned JBDS-3635: ----------------------------------- Assignee: Denis Golovin > Add the ability to detect/select existing dependencies/tools > ------------------------------------------------------------ > > Key: JBDS-3635 > URL: https://issues.jboss.org/browse/JBDS-3635 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Reporter: Jan Richter > Assignee: Denis Golovin > Labels: havoc, ui > Attachments: pdkinstaller.png > > > It would be great if the installer allowed the user to use some of the required tools they have already installed. > The idea is to detect if the dependencies are already present and let the user decide if they want to use them, or install new ones. Also, it could let the user select the tools themselves if they want to use a different installation than detected, etc. > The confirmation page we currently have looks like the place to put all this, since it already displays most of the stuff that is going to get installed. Anyway, I have tried to modify it and squeeze the controls in and this is how the selection turned out (imagine the messages looking a bit smarter): > !pdkinstaller.png|thumbnail! > [~dgolovin] & [~crobson], what's your opinion on this? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3643) Installer - Should display a unique build identifier

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3643?page=com.atlassian.jira.plugin.... ] Denis Golovin reassigned JBDS-3643: ----------------------------------- Assignee: Joshua Wilson > Installer - Should display a unique build identifier > ----------------------------------------------------- > > Key: JBDS-3643 > URL: https://issues.jboss.org/browse/JBDS-3643 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.GA > Reporter: Len DiMaggio > Assignee: Joshua Wilson > Labels: havoc, ui > > This affects QE immediately, and may affect customers too. The installer UI should display a unique identifier (version number). Having a build number displayed in the UI will assist QE in testing as we iterate through the various versions of the installer. Thx! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3655) Installer should handle reboot requests from virtual box msi installation

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3655?page=com.atlassian.jira.plugin.... ] Denis Golovin reassigned JBDS-3655: ----------------------------------- Assignee: Denis Golovin > Installer should handle reboot requests from virtual box msi installation > ------------------------------------------------------------------------- > > Key: JBDS-3655 > URL: https://issues.jboss.org/browse/JBDS-3655 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Reporter: Denis Golovin > Assignee: Denis Golovin > Labels: havoc > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3620) Account page should take into consideration that login request can be long term operation

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3620?page=com.atlassian.jira.plugin.... ] Denis Golovin reassigned JBDS-3620: ----------------------------------- Assignee: Joshua Wilson (was: Denis Golovin) > Account page should take into consideration that login request can be long term operation > ----------------------------------------------------------------------------------------- > > Key: JBDS-3620 > URL: https://issues.jboss.org/browse/JBDS-3620 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Reporter: Denis Golovin > Assignee: Joshua Wilson > Priority: Critical > Labels: havoc, ui > Fix For: 9.1.0.CR1 > > > Would be good to: > 1. Show progress animation; > 2. Lock [Log In] button; > 3. Have a timeout for login operation with error show in the end and button unlocked for another attempt. > Currently auth fails in browser with error below > {code}Gateway Timeout > The proxy server did not receive a timely response from the upstream server. > Reference #1.5434d417.1452674127.644f0c55 > {code} > which makes installer to look like being in broken state: > - no errors; > - [Log In] can be pressed many times without any reaction -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

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 March 2016