March 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3629) Installer - When an install fails, the error is indicated to the user in a subtle manner in the UI

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3629?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3629: ------------------------------------- JBDS-3631 seems to be a duplicate. > Installer - When an install fails, the error is indicated to the user in a subtle manner in the UI > -------------------------------------------------------------------------------------------------- > > Key: JBDS-3629 > URL: https://issues.jboss.org/browse/JBDS-3629 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: installer > Reporter: Len DiMaggio > Labels: havoc > Fix For: 9.1.0.CR1 > > Attachments: install.log, install_error.png, install_error.png > > > The error is indicated in the same size/color text - a user might miss this. Can we make the errors more obvious? Thx! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3631) When an install fails, the user is able to view the error log to debug the cause of the failure, but the UI does not display any details

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3631?page=com.atlassian.jira.plugin.... ] Denis Golovin reassigned JBDS-3631: ----------------------------------- Assignee: Denis Golovin > When an install fails, the user is able to view the error log to debug the cause of the failure, but the UI does not display any details > ---------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3631 > URL: https://issues.jboss.org/browse/JBDS-3631 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: installer > Reporter: Len DiMaggio > Assignee: Denis Golovin > Labels: havoc > Fix For: 9.1.0.CR1 > > Attachments: install_error.png > > > It would be helpful to provide the user either a summary of the last failure, or a window that displays the install log, inside the installer UI. Thx! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

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 commented on JBDS-3635: ------------------------------------- [~jrichter1], looks good to me, could you share the branch or send PR? > 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 > Labels: havoc > 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)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3637) Bundled installer

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3637?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3637: ------------------------------------- Method that called to include binaries into electron generated installer https://github.com/Squirrel/Squirrel.Windows/blob/master/src/Update/Progr... > Bundled installer > ----------------- > > Key: JBDS-3637 > URL: https://issues.jboss.org/browse/JBDS-3637 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Reporter: Ken Finnigan > Assignee: Denis Golovin > Priority: Critical > Labels: havoc > Fix For: 9.1.0.CR1 > > > Provide a version of the installer with all pieces already included, so no downloads are required, for all pieces that have an appropriate license. > VirtualBox will always need to be downloaded, unless we build from source. > JBDS can not be bundled until https://issues.jboss.org/browse/JBDS-3557 is resolved. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3638) Update to official CDK v2 release

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3638?page=com.atlassian.jira.plugin.... ] Denis Golovin reassigned JBDS-3638: ----------------------------------- Assignee: Denis Golovin > Update to official CDK v2 release > --------------------------------- > > Key: JBDS-3638 > URL: https://issues.jboss.org/browse/JBDS-3638 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: installer > Reporter: Ken Finnigan > Assignee: Denis Golovin > Priority: Blocker > Labels: havoc > Fix For: 9.1.0.CR1 > > > Modify https://github.com/redhat-developer-tooling/developer-platform-install/bl... to point to the CDK v2 box when a new release is available in Customer Portal. > Also change to use commented out downloadAuth() call for CDK box to provide appropriate authentication: https://github.com/redhat-developer-tooling/developer-platform-install/bl... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3646) Download VirtualBox and Vagrant

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3646?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3646: ------------------------------------- Can we download original vagrant installer instead of downloading one we built our self? > Download VirtualBox and Vagrant > ------------------------------- > > Key: JBDS-3646 > URL: https://issues.jboss.org/browse/JBDS-3646 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Reporter: Pete Muir > Assignee: Denis Golovin > Priority: Blocker > Labels: havoc > Fix For: 9.1.0.GA > > > We must always download VirtualBox and vagrant, regardless of whether we build a downloading installer, or a bundled installer. > This is an IP requirement -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3647) Investigate why we are including both cygwin and mingw

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3647?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3647: ------------------------------------- MinGW is part of Vagrant distribution. Vagrant distribution gets MinGW from Ruby DevKit. [CHAPTER 3. INSTALLING THE CDK ON MICROSOFT WINDOWS|https://access.redhat.com/documentation/en/red-hat-enterprise-lin...] : {quote}It is recommended that you install the Cygwin environment from cygwin.com to provide the ssh and rsync tools for use by Vagrant{quote} {quote}With the Vagrant box and Vagrantfiles in place, you are ready to bring up the selected Vagrant box. You can use a pre-defined Vagrantfile to initialize the box or you can just initialize the box and create your own Vagrant file. In order to run the following steps, you need to have ssh.exe and rsync.exe in your path from installing Cygwin (or your choice of Linux-like utilities).{quote} > Investigate why we are including both cygwin and mingw > ------------------------------------------------------ > > Key: JBDS-3647 > URL: https://issues.jboss.org/browse/JBDS-3647 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Reporter: Pete Muir > Priority: Critical > Labels: havoc > Fix For: 9.1.0.CR1 > > > We shouldn't need to include cygwin to make vagrant work. Let's check why we include this. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 9 months

1
0
0 / 0

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

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21731?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-21731: --------------------------------------- [~adietish] [~scabanovich] this https://github.com/openshift/openshift-restclient-java/pull/118 provides a way to retieve tag and metadata for an image assuming the openshift cluster can resolve the full docker tag. You can explicitly grab the image metadata that you require if you needed. > Server Adapter: Error shown when image is not created/pushed yet, could be more user friendly > --------------------------------------------------------------------------------------------- > > Key: JBIDE-21731 > URL: https://issues.jboss.org/browse/JBIDE-21731 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > 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. > Screenshot of error: > !cannot_get_image.png! > 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)

8 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues March 2016