January 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-12116) Cannot cancel Verifying SSH session job's dialog

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12116?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-12116: ------------------------------------- Fix Version/s: 4.1.x (was: 4.0.x) > Cannot cancel Verifying SSH session job's dialog > ------------------------------------------------ > > Key: JBIDE-12116 > URL: https://issues.jboss.org/browse/JBIDE-12116 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 3.3.0.CR1 > Reporter: Lucia Jelinkova > Assignee: Xavier Coulon > Priority: Minor > Fix For: 4.1.x > > Attachments: dialog.jpg > > > When the Port forwarding is invoked from Openshift Explorer for the first time a job is triggered (Verifying SSH session to retrieve Application's ports...) and a dialog is displayed. User can run the job on backgroud, show details and cancel the job. However, when Cancel is pressed the Port forwarding dialog is shown anyway. > !dialog.jpg! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12069) NPE when cancelling the Domain creation as part of an Application creation

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12069?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-12069: ------------------------------------- Fix Version/s: 4.1.x (was: 4.0.x) > NPE when cancelling the Domain creation as part of an Application creation > --------------------------------------------------------------------------- > > Key: JBIDE-12069 > URL: https://issues.jboss.org/browse/JBIDE-12069 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 3.3.0.CR1 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Priority: Minor > Fix For: 4.1.x > > > java.lang.NullPointerException > at org.eclipse.jface.window.Window.initializeBounds(Window.java:758) > at org.eclipse.jface.dialogs.Dialog.initializeBounds(Dialog.java:714) > at org.eclipse.jface.window.Window.create(Window.java:435) > at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1089) > at org.eclipse.jface.window.Window.open(Window.java:790) > at org.jboss.tools.openshift.express.internal.ui.action.CreateApplicationAction.run(CreateApplicationAction.java:49) > at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) > at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) > at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) > at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4128) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1457) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1480) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1465) > at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1270) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3974) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3613) > at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701) > at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665) > at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) > at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) > at org.eclipse.equinox.launcher.Main.run(Main.java:1410) > at org.eclipse.equinox.launcher.Main.main(Main.java:1386) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12305) Log in page in application wizard should auto-complete/suggest existing users when typing

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12305?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-12305. -------------------------------------- Resolution: Out of Date This issue is outdated. The 1st wizard page with the credentials is now completely different. It allows you to select an existing connection from a combo or to create a new one: !use-existing-connection.png! > Log in page in application wizard should auto-complete/suggest existing users when typing > ------------------------------------------------------------------------------------------ > > Key: JBIDE-12305 > URL: https://issues.jboss.org/browse/JBIDE-12305 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 3.3.0.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.0.x > > Attachments: use-existing-connection.png > > > When launching the application wizard from central you get to the 1st wizard page where you have to enter your credentials. If you have several users in OpenShift Explorer, then it's pretty much tedious to switch between them. The input-fields dont assist you at all. You have to fill in the whole username and password. The username could suggest usernames that exist in the OpenShift Explorer in a list (like search suggestions in google or any other web-site) that you could navigate and select instead of having to type the whole name again. The password could then get autofilled from the eclipse secure storage. That would spare a lot of typing and would be pretty handy if you have several users you work with. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12305) Log in page in application wizard should auto-complete/suggest existing users when typing

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12305?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-12305: ------------------------------------- Attachment: use-existing-connection.png > Log in page in application wizard should auto-complete/suggest existing users when typing > ------------------------------------------------------------------------------------------ > > Key: JBIDE-12305 > URL: https://issues.jboss.org/browse/JBIDE-12305 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 3.3.0.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.0.x > > Attachments: use-existing-connection.png > > > When launching the application wizard from central you get to the 1st wizard page where you have to enter your credentials. If you have several users in OpenShift Explorer, then it's pretty much tedious to switch between them. The input-fields dont assist you at all. You have to fill in the whole username and password. The username could suggest usernames that exist in the OpenShift Explorer in a list (like search suggestions in google or any other web-site) that you could navigate and select instead of having to type the whole name again. The password could then get autofilled from the eclipse secure storage. That would spare a lot of typing and would be pretty handy if you have several users you work with. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12312) If domain creation fails because of name that's already used, no info is visible in wizard after you closed the error dialog

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12312?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-12312: ------------------------------------------ In 4.0.0.Final the Domain creation wizard has no widgets for the ssh key anymore. Nevertheless, this issue is still valid. Once you close the error, you dont see what's wrong with the current name. !no-error.png! *Finish* should be disabled as long as you dont change the name. > If domain creation fails because of name that's already used, no info is visible in wizard after you closed the error dialog > ---------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-12312 > URL: https://issues.jboss.org/browse/JBIDE-12312 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 3.3.0.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.0.x > > Attachments: domain-name-already-used.png, missing-user-guidance.png, no-error.png > > > If you create a new domain on OpenShift, you'll have to provide it's name. This name has to be unique across OpenShift (for all users). If you use a domain name that's already used, you'll get an error dialog that informs you about the name not being unique across OpenShift. > !domain-name-already-used.png! > Once you close this dialog, noting is showing this error any more. The name field is not decorated with an error marker. > steps to reproduce: > # ASSERT make sure you have an account without a domain > # EXEC launch the *OpenShift Application* wizard > # ASSERT you get to the *Domain creation* dialog > # EXEC supply a valid key and choose a domain name that is *already used* (ex. "domain") > # ASSERT You get an error dialog that tells you that the domain name is already used > # EXEC hit *OK* > Result: > The domain creation dialog has no information that would tell you what you have to correct. > !missing-user-guidance.png! > We should improved this: > * put an error decoration to the name text field > * put the cursor into the name text field (eventually select the whole name in it) > * eventually reach out to #libra to get a way to query the availability of the given name, so that we can validate while typing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12312) If domain creation fails because of name that's already used, no info is visible in wizard after you closed the error dialog

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12312?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-12312: ------------------------------------- Attachment: no-error.png > If domain creation fails because of name that's already used, no info is visible in wizard after you closed the error dialog > ---------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-12312 > URL: https://issues.jboss.org/browse/JBIDE-12312 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 3.3.0.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.0.x > > Attachments: domain-name-already-used.png, missing-user-guidance.png, no-error.png > > > If you create a new domain on OpenShift, you'll have to provide it's name. This name has to be unique across OpenShift (for all users). If you use a domain name that's already used, you'll get an error dialog that informs you about the name not being unique across OpenShift. > !domain-name-already-used.png! > Once you close this dialog, noting is showing this error any more. The name field is not decorated with an error marker. > steps to reproduce: > # ASSERT make sure you have an account without a domain > # EXEC launch the *OpenShift Application* wizard > # ASSERT you get to the *Domain creation* dialog > # EXEC supply a valid key and choose a domain name that is *already used* (ex. "domain") > # ASSERT You get an error dialog that tells you that the domain name is already used > # EXEC hit *OK* > Result: > The domain creation dialog has no information that would tell you what you have to correct. > !missing-user-guidance.png! > We should improved this: > * put an error decoration to the name text field > * put the cursor into the name text field (eventually select the whole name in it) > * eventually reach out to #libra to get a way to query the availability of the given name, so that we can validate while typing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12312) If domain creation fails because of name that's already used, no info is visible in wizard after you closed the error dialog

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12312?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-12312: ------------------------------------- Fix Version/s: 4.1.x (was: 4.0.x) > If domain creation fails because of name that's already used, no info is visible in wizard after you closed the error dialog > ---------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-12312 > URL: https://issues.jboss.org/browse/JBIDE-12312 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 3.3.0.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.1.x > > Attachments: domain-name-already-used.png, missing-user-guidance.png, no-error.png > > > If you create a new domain on OpenShift, you'll have to provide it's name. This name has to be unique across OpenShift (for all users). If you use a domain name that's already used, you'll get an error dialog that informs you about the name not being unique across OpenShift. > !domain-name-already-used.png! > Once you close this dialog, noting is showing this error any more. The name field is not decorated with an error marker. > steps to reproduce: > # ASSERT make sure you have an account without a domain > # EXEC launch the *OpenShift Application* wizard > # ASSERT you get to the *Domain creation* dialog > # EXEC supply a valid key and choose a domain name that is *already used* (ex. "domain") > # ASSERT You get an error dialog that tells you that the domain name is already used > # EXEC hit *OK* > Result: > The domain creation dialog has no information that would tell you what you have to correct. > !missing-user-guidance.png! > We should improved this: > * put an error decoration to the name text field > * put the cursor into the name text field (eventually select the whole name in it) > * eventually reach out to #libra to get a way to query the availability of the given name, so that we can validate while typing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12322) error detail message is null if domain creation fails with 500

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12322?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-12322. -------------------------------------- Fix Version/s: 4.1.0.Alpha1 (was: 4.0.x) Resolution: Out of Date > error detail message is null if domain creation fails with 500 > -------------------------------------------------------------- > > Key: JBIDE-12322 > URL: https://issues.jboss.org/browse/JBIDE-12322 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 3.3.0.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.1.0.Alpha1 > > Attachments: null-detail-error.png > > > If the domain creation fails with 500, you'll spot a *null* in the detail of the error message: > !null-detail-error.png! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12322) error detail message is null if domain creation fails with 500

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12322?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-12322: ------------------------------------------ Cannot reproduce this in 4.0.0.Final, setting to *Out of Date* > error detail message is null if domain creation fails with 500 > -------------------------------------------------------------- > > Key: JBIDE-12322 > URL: https://issues.jboss.org/browse/JBIDE-12322 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 3.3.0.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.1.0.Alpha1 > > Attachments: null-detail-error.png > > > If the domain creation fails with 500, you'll spot a *null* in the detail of the error message: > !null-detail-error.png! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12321) handle IApplication#getEmbeddedCartridges correctly with changes to protocol 1.1

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12321?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-12321: ------------------------------------- Fix Version/s: 4.1.x (was: 4.1.0.Alpha1) > handle IApplication#getEmbeddedCartridges correctly with changes to protocol 1.1 > -------------------------------------------------------------------------------- > > Key: JBIDE-12321 > URL: https://issues.jboss.org/browse/JBIDE-12321 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 4.0.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.1.x > > Attachments: app-type-listed-as-embedded.png > > > In 1.1 the cartridges that you get reported when listing them on a application changed (IApplication#getEmbeddedCartridges): > * 1.0: > would report the embedded cartridges only > * 1.1: > would report the embedded cartridges and the application type (cartridge) > !app-type-listed-as-embedded.png! > see here: https://github.com/openshift/crankcase/pull/224 > The error that this caused was discussed here: > https://bugzilla.redhat.com/show_bug.cgi?id=838611 > OpenShift pushed the discussed change (application-type reported as embedded cartridge) to protocol v1.1 and fixed the issue on the server-side. Our client, that currently requests protocol v1.0 has no issue since the fix. We have to make sure we support protocol 1.1 and are able to handle this correctly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 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 January 2013