[JBoss JIRA] (JBIDE-16041) "null" in label of remove connection dialog
by Marián Labuda (JIRA)
Marián Labuda created JBIDE-16041:
-------------------------------------
Summary: "null" in label of remove connection dialog
Key: JBIDE-16041
URL: https://issues.jboss.org/browse/JBIDE-16041
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.1.1.CR1
Reporter: Marián Labuda
Assignee: Andre Dietisheim
Priority: Minor
Attachments: null_label.png
In prompt (after attempt to remove OpenShift connection in OpenShift Explorer) is in dialog shown some text tooltip but there is some "null" value.
--
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
12 years, 5 months
[JBoss JIRA] (JBIDE-16041) "null" in label of remove connection dialog
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16041?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-16041:
----------------------------------
Description:
In prompt (after attempt to remove OpenShift connection in OpenShift Explorer) is in dialog shown some text tooltip but there is some "null" value.
!null_label.png!
was:
In prompt (after attempt to remove OpenShift connection in OpenShift Explorer) is in dialog shown some text tooltip but there is some "null" value.
> "null" in label of remove connection dialog
> -------------------------------------------
>
> Key: JBIDE-16041
> URL: https://issues.jboss.org/browse/JBIDE-16041
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.1.CR1
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Priority: Minor
> Attachments: null_label.png
>
>
> In prompt (after attempt to remove OpenShift connection in OpenShift Explorer) is in dialog shown some text tooltip but there is some "null" value.
> !null_label.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
12 years, 5 months
[JBoss JIRA] (JBIDE-16040) Openshift Enterprise: Web balancer cartridge should not be listed
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16040?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-16040:
----------------------------------
Attachment: haproxy_cartridge.png
> Openshift Enterprise: Web balancer cartridge should not be listed
> -----------------------------------------------------------------
>
> Key: JBIDE-16040
> URL: https://issues.jboss.org/browse/JBIDE-16040
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.1.1.CR1
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Attachments: haproxy_cartridge.png
>
>
> There is embedded cartridge Web Balancer listed in table of embedded cartridges. It is not possible use this cartridge in any application, bcs. it's automatically added to scalable application. Remove this cartridge from scalable application is not possible as well. Also on the OpenShift Enterprise is not this cartridge listed among others.
--
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
12 years, 5 months
[JBoss JIRA] (JBIDE-16040) Openshift Enterprise: Web balancer cartridge should not be listed
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16040?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-16040:
----------------------------------
Description:
There is embedded cartridge Web Balancer listed in table of embedded cartridges. It is not possible use this cartridge in any application, bcs. it's automatically added to scalable application. Remove this cartridge from scalable application is not possible as well. Also on the OpenShift Enterprise is not this cartridge listed among others.
!haproxy_cartridge.png!
was:There is embedded cartridge Web Balancer listed in table of embedded cartridges. It is not possible use this cartridge in any application, bcs. it's automatically added to scalable application. Remove this cartridge from scalable application is not possible as well. Also on the OpenShift Enterprise is not this cartridge listed among others.
> Openshift Enterprise: Web balancer cartridge should not be listed
> -----------------------------------------------------------------
>
> Key: JBIDE-16040
> URL: https://issues.jboss.org/browse/JBIDE-16040
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.1.1.CR1
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Attachments: haproxy_cartridge.png
>
>
> There is embedded cartridge Web Balancer listed in table of embedded cartridges. It is not possible use this cartridge in any application, bcs. it's automatically added to scalable application. Remove this cartridge from scalable application is not possible as well. Also on the OpenShift Enterprise is not this cartridge listed among others.
> !haproxy_cartridge.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
12 years, 5 months
[JBoss JIRA] (JBIDE-16040) Openshift Enterprise: Web balancer cartridge should not be listed
by Marián Labuda (JIRA)
Marián Labuda created JBIDE-16040:
-------------------------------------
Summary: Openshift Enterprise: Web balancer cartridge should not be listed
Key: JBIDE-16040
URL: https://issues.jboss.org/browse/JBIDE-16040
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 4.1.1.CR1
Reporter: Marián Labuda
Assignee: Andre Dietisheim
There is embedded cartridge Web Balancer listed in table of embedded cartridges. It is not possible use this cartridge in any application, bcs. it's automatically added to scalable application. Remove this cartridge from scalable application is not possible as well. Also on the OpenShift Enterprise is not this cartridge listed among others.
--
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
12 years, 5 months
[JBoss JIRA] (JBIDE-16039) Environment variables persists in manager after delete
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16039?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-16039:
----------------------------------
Description:
ASSERT: Have connection with domain and app on server supporting environment variables.
EXEC: Open application context menu and choose Edit environment variables
EXEC: Create new environment variable.
EXEC: Show all environment variables
ASSERT: New variable is shown.
EXEC: Open Edit environment variables and remove that environment variable.
EXEC: Show all environment variables
ASSERT: Removed variable is not presented
ASSERT: Open Edit environment variables and assert that variable is not presented there too.
In last assert environment variable is shown in table of variables, although it has been successfully removed.
Screenshot has been taken in last assert
!env_vars_bug.png!
was:
ASSERT: Have connection with domain and app on server supporting environment variables.
EXEC: Open application context menu and choose Edit environment variables
EXEC: Create new environment variable.
EXEC: Show all environment variables
ASSERT: New variable is shown.
EXEC: Open Edit environment variables and remove that environment variable.
EXEC: Show all environment variables
ASSERT: Removed variable is not presented
ASSERT: Open Edit environment variables and assert that variable is not presented there too.
In last assert environment variable is shown in table of variables, although it has been successfully removed.
Screenshot has been taken in last assert !env_vars_bug.png!
> Environment variables persists in manager after delete
> ------------------------------------------------------
>
> Key: JBIDE-16039
> URL: https://issues.jboss.org/browse/JBIDE-16039
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.1.CR1
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Attachments: env_vars_bug.png
>
>
> ASSERT: Have connection with domain and app on server supporting environment variables.
> EXEC: Open application context menu and choose Edit environment variables
> EXEC: Create new environment variable.
> EXEC: Show all environment variables
> ASSERT: New variable is shown.
> EXEC: Open Edit environment variables and remove that environment variable.
> EXEC: Show all environment variables
> ASSERT: Removed variable is not presented
> ASSERT: Open Edit environment variables and assert that variable is not presented there too.
> In last assert environment variable is shown in table of variables, although it has been successfully removed.
> Screenshot has been taken in last assert
> !env_vars_bug.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
12 years, 5 months
[JBoss JIRA] (JBIDE-16032) java.lang.ArrayIndexOutOfBoundsException in Forge Runtime preferences
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16032?page=com.atlassian.jira.plugi... ]
Pavol Srna updated JBIDE-16032:
-------------------------------
Assignee: Koen Aers
> java.lang.ArrayIndexOutOfBoundsException in Forge Runtime preferences
> ---------------------------------------------------------------------
>
> Key: JBIDE-16032
> URL: https://issues.jboss.org/browse/JBIDE-16032
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Reporter: Pavol Srna
> Assignee: Koen Aers
> Labels: respin-a
> Fix For: 4.1.1.CR1
>
> Attachments: forge-preferences.png
>
>
> Stacktrace:
> {code}
> java.lang.ArrayIndexOutOfBoundsException: 0
> at org.jboss.tools.forge.ui.preferences.ForgeInstallationsPreferencePage$6.run(ForgeInstallationsPreferencePage.java:293)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.jboss.tools.forge.ui.preferences.ForgeInstallationsPreferencePage.performOk(ForgeInstallationsPreferencePage.java:290)
> at org.eclipse.jface.preference.PreferenceDialog$13.run(PreferenceDialog.java:965)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49)
> at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)
> at org.eclipse.jface.preference.PreferenceDialog.okPressed(PreferenceDialog.java:945)
> at org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.okPressed(FilteredPreferenceDialog.java:448)
> at org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.okPressed(WorkbenchPreferenceDialog.java:171)
> at org.eclipse.jface.preference.PreferenceDialog.buttonPressed(PreferenceDialog.java:233)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:628)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1392)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3742)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:826)
> at org.eclipse.jface.window.Window.open(Window.java:802)
> at org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.open(WorkbenchPreferenceDialog.java:215)
> at org.eclipse.ui.internal.OpenPreferencesAction.run(OpenPreferencesAction.java:65)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:499)
> 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.Widget.sendEvent(Widget.java:1392)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3742)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> 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:354)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
> {code}
--
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
12 years, 5 months
[JBoss JIRA] (JBIDE-16039) Environment variables persists in manager after delete
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16039?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-16039:
----------------------------------
Attachment: env_vars_bug.png
> Environment variables persists in manager after delete
> ------------------------------------------------------
>
> Key: JBIDE-16039
> URL: https://issues.jboss.org/browse/JBIDE-16039
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.1.CR1
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Attachments: env_vars_bug.png
>
>
> ASSERT: Have connection with domain and app on server supporting environment variables.
> EXEC: Open application context menu and choose Edit environment variables
> EXEC: Create new environment variable.
> EXEC: Show all environment variables
> ASSERT: New variable is shown.
> EXEC: Open Edit environment variables and remove that environment variable.
> EXEC: Show all environment variables
> ASSERT: Removed variable is not presented
> ASSERT: Open Edit environment variables and assert that variable is not presented there too.
> In last assert environment variable is shown in table of variables, although it has been successfully removed.
> See attached file (screen shot taken in last assert).
--
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
12 years, 5 months