[JBoss JIRA] (JBIDE-21678) New Connection wizard: Getting started info is not visible by default
by Marián Labuda (JIRA)
Marián Labuda created JBIDE-21678:
-------------------------------------
Summary: New Connection wizard: Getting started info is not visible by default
Key: JBIDE-21678
URL: https://issues.jboss.org/browse/JBIDE-21678
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.1.CR1
Reporter: Marián Labuda
Attachments: default_new_conn.png, rendered_new_conn.png
In opened New Connection wizard there is supposed to be getting started text leading to either sign in page for OpenShift 2 or to getting started content for OpenShift 3, but it it empty by default. Upon changing e.g. server type or checking/unchecking Use default server checkbox, the text appears. Resizing window does not fix the problem. This is also happening when editing an existing OpenShift 3 connection (via context menu of a connection).
See screenshot of fresh opened New Connection wizard:
!default_new_conn.png!
and after checkbox is (un)checked or server type is changed:
!rendered_new_conn.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21678) New Connection wizard: Getting started info is not visible by default
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21678?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-21678:
----------------------------------
Labels: connection_wizard (was: )
> New Connection wizard: Getting started info is not visible by default
> ----------------------------------------------------------------------
>
> Key: JBIDE-21678
> URL: https://issues.jboss.org/browse/JBIDE-21678
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Labels: connection_wizard, openshift_v2, openshift_v3
> Attachments: default_new_conn.png, rendered_new_conn.png
>
>
> In opened New Connection wizard there is supposed to be getting started text leading to either sign in page for OpenShift 2 or to getting started content for OpenShift 3, but it it empty by default. Upon changing e.g. server type or checking/unchecking Use default server checkbox, the text appears. Resizing window does not fix the problem. This is also happening when editing an existing OpenShift 3 connection (via context menu of a connection).
> See screenshot of fresh opened New Connection wizard:
> !default_new_conn.png!
> and after checkbox is (un)checked or server type is changed:
> !rendered_new_conn.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21678) New Connection wizard: Getting started info is not visible by default
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21678?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-21678:
----------------------------------
Labels: connection_wizard openshift_v2 openshift_v3 (was: connection_wizard)
> New Connection wizard: Getting started info is not visible by default
> ----------------------------------------------------------------------
>
> Key: JBIDE-21678
> URL: https://issues.jboss.org/browse/JBIDE-21678
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Labels: connection_wizard, openshift_v2, openshift_v3
> Attachments: default_new_conn.png, rendered_new_conn.png
>
>
> In opened New Connection wizard there is supposed to be getting started text leading to either sign in page for OpenShift 2 or to getting started content for OpenShift 3, but it it empty by default. Upon changing e.g. server type or checking/unchecking Use default server checkbox, the text appears. Resizing window does not fix the problem. This is also happening when editing an existing OpenShift 3 connection (via context menu of a connection).
> See screenshot of fresh opened New Connection wizard:
> !default_new_conn.png!
> and after checkbox is (un)checked or server type is changed:
> !rendered_new_conn.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21677) Change branding for EAP server types
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-21677:
-----------------------------------
Summary: Change branding for EAP server types
Key: JBIDE-21677
URL: https://issues.jboss.org/browse/JBIDE-21677
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: server
Affects Versions: 4.3.1.Beta2
Reporter: Rob Stryker
1) Change branding for EAP small icon to shadowman. Ask Catherine
2) Change name to "Red Hat JBoss Enterprise Application Platform x.y"
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21673) JBoss Runtime Detection preference page throws StackOverflowError
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21673?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-21673:
-------------------------------------
The base patch looks ok. I'll need to run through and test it to verify.
> JBoss Runtime Detection preference page throws StackOverflowError
> -----------------------------------------------------------------
>
> Key: JBIDE-21673
> URL: https://issues.jboss.org/browse/JBIDE-21673
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, runtime-detection
> Affects Versions: 4.3.1.Beta2
> Reporter: Viacheslav Kabanovich
> Fix For: 4.3.1.CR1, 4.4.0.Alpha1
>
>
> 1. Start Eclipse.
> 2. Open Preferences.
> 3. Select JBoss Runtime Detection.
> Exception:
> {code}
> !ENTRY org.eclipse.ui 4 0 2016-02-10 19:18:24.266
> !MESSAGE Unhandled event loop exception
> !STACK 0
> org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.StackOverflowError)
> at org.eclipse.swt.SWT.error(SWT.java:4503)
> at org.eclipse.swt.SWT.error(SWT.java:4418)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3795)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3434)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:818)
> at org.eclipse.jface.window.Window.open(Window.java:794)
> at org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.open(WorkbenchPreferenceDialog.java:211)
> at org.eclipse.ui.internal.OpenPreferencesAction.run(OpenPreferencesAction.java:63)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:473)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:564)
> at org.eclipse.jface.action.ActionContributionItem.lambda$4(ActionContributionItem.java:396)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4482)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3820)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3431)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1132)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1023)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:157)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:651)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:595)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:670)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:609)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1516)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1489)
> Caused by: java.lang.StackOverflowError
> at org.eclipse.swt.internal.gtk.OS._gtk_widget_size_allocate(Native Method)
> at org.eclipse.swt.internal.gtk.OS.gtk_widget_size_allocate(OS.java:14919)
> ----infinitle repeated part begin----
> at org.eclipse.swt.custom.TableEditor$1.controlMoved(TableEditor.java:95)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:224)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4482)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1353)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1334)
> at org.eclipse.swt.widgets.TableColumn.gtk_size_allocate(TableColumn.java:395)
> at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:1991)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:4718)
> at org.eclipse.swt.internal.gtk.OS._gtk_widget_size_allocate(Native Method)
> at org.eclipse.swt.internal.gtk.OS.gtk_widget_size_allocate(OS.java:14919)
> at org.eclipse.swt.widgets.Control.forceResize(Control.java:780)
> at org.eclipse.swt.widgets.Table.getClientArea(Table.java:1154)
> at org.eclipse.swt.custom.TableEditor.computeBounds(TableEditor.java:120)
> at org.eclipse.swt.custom.ControlEditor.layout(ControlEditor.java:223)
> at org.eclipse.swt.custom.TableEditor.layout(TableEditor.java:265)
> at org.eclipse.swt.custom.TableEditor$1.controlMoved(TableEditor.java:95)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:224)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4482)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1353)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1334)
> at org.eclipse.swt.widgets.TableColumn.gtk_size_allocate(TableColumn.java:395)
> at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:1991)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:4718)
> at org.eclipse.swt.internal.gtk.OS._gtk_widget_size_allocate(Native Method)
> at org.eclipse.swt.internal.gtk.OS.gtk_widget_size_allocate(OS.java:14919)
> at org.eclipse.swt.widgets.Control.forceResize(Control.java:780)
> at org.eclipse.swt.widgets.Table.getClientArea(Table.java:1154)
> at org.eclipse.swt.custom.TableEditor.computeBounds(TableEditor.java:120)
> at org.eclipse.swt.custom.ControlEditor.layout(ControlEditor.java:223)
> at org.eclipse.swt.custom.TableEditor.layout(TableEditor.java:265)
> ----infinitle repeated part end----
> at org.eclipse.swt.custom.ControlEditor.setEditor(ControlEditor.java:251)
> at org.eclipse.swt.custom.TableEditor.setEditor(TableEditor.java:240)
> at org.eclipse.swt.custom.TableEditor.setEditor(TableEditor.java:256)
> at org.jboss.tools.runtime.ui.internal.preferences.RuntimePreferencePage.createDetectorViewer(RuntimePreferencePage.java:208)
> at org.jboss.tools.runtime.ui.internal.preferences.RuntimePreferencePage.createContents(RuntimePreferencePage.java:140)
> at org.eclipse.jface.preference.PreferencePage.createControl(PreferencePage.java:241)
> at org.eclipse.jface.preference.PreferenceDialog.createPageControl(PreferenceDialog.java:1429)
> at org.eclipse.jface.preference.PreferenceDialog$9.run(PreferenceDialog.java:1196)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50)
> at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173)
> at org.eclipse.jface.preference.PreferenceDialog.showPage(PreferenceDialog.java:1188)
> at org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.showPage(FilteredPreferenceDialog.java:608)
> at org.eclipse.jface.preference.PreferenceDialog$5.lambda$0(PreferenceDialog.java:655)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.jface.preference.PreferenceDialog$5.selectionChanged(PreferenceDialog.java:652)
> at org.eclipse.jface.viewers.StructuredViewer$3.run(StructuredViewer.java:876)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50)
> at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173)
> at org.eclipse.jface.viewers.StructuredViewer.firePostSelectionChanged(StructuredViewer.java:873)
> at org.eclipse.jface.viewers.StructuredViewer.handlePostSelect(StructuredViewer.java:1242)
> at org.eclipse.jface.viewers.StructuredViewer$5.widgetSelected(StructuredViewer.java:1268)
> at org.eclipse.jface.util.OpenStrategy.firePostSelectionEvent(OpenStrategy.java:265)
> at org.eclipse.jface.util.OpenStrategy.access$5(OpenStrategy.java:259)
> at org.eclipse.jface.util.OpenStrategy$1.lambda$1(OpenStrategy.java:431)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> ... 36 more
> {code}
> 4. Select another preference page.
> 5. Again try to select JBoss Runtime Detection.
> Now, it opens successfully.
> 6. Try to adjust split between the tree of pages and the page.
> Preferences dialog window starts uncontrollably expand until it fills the entire screen width.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21341) Credentials: Allow to show password even if you choose to save it
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21341?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-21341:
-------------------------------------
Screenshot looks good, will review code.
> Credentials: Allow to show password even if you choose to save it
> -----------------------------------------------------------------
>
> Key: JBIDE-21341
> URL: https://issues.jboss.org/browse/JBIDE-21341
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: common/jst/core
> Affects Versions: 4.3.1.Beta1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.3.1.CR1
>
> Attachments: AddCredential.png
>
>
> When you add credentials for access.redhat.com account to be used with CDK adapter, you can choose to only save your username and enter password each time. In that case when that happens, you can choose to show the password as you type (i.e. no ****). I think to be consistent you should allow the same when you're creating the credentials and enter the password there.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21674) Enable hierarchical view by default in Project Explorer
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21674?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-21674:
----------------------------------------
That's right, changing the activeByDefault and some other default values in the pom.xml of org.eclipse.ui.navigator.resources seems to be the simplest approach. However, this would als affect Eclipse IDE for all users, and we prefer avoiding such changes until the users seem to want it. Indeed, people have their habits, but the main reason IMO is that the NestedProjectContentProvider consume resources, that may not be suitable in some case.
So at the moment, any solution that involves changing the default behavior inside the plugin directly is currently "too intrusive" to be changed directly in the Eclipse IDE now.
> Enable hierarchical view by default in Project Explorer
> -------------------------------------------------------
>
> Key: JBIDE-21674
> URL: https://issues.jboss.org/browse/JBIDE-21674
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: common/jst/core
> Reporter: Xavier Coulon
>
> Project Explorer has been supporting hierarchical view of projects since Mars, but this is not enabled by default in Eclipse (core) even though this is a valuable features, especially for Maven projects that include modules (ie, sub-projects).
> After discussing about it with [~mickael_istria] and [~nickboldt], we should see if we can enable this setting by default in DevStudio.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month