[JBoss JIRA] (JBIDE-21302) Removing user from credentials framework while not authenticated to secure storage should not work
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21302?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-21302:
--------------------------------
Fix Version/s: 4.4.0.Alpha1
> Removing user from credentials framework while not authenticated to secure storage should not work
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21302
> URL: https://issues.jboss.org/browse/JBIDE-21302
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common/jst/core
> Affects Versions: 4.3.1.Beta1
> Environment: JBDS 9.0.0.Beta1-v20151210-1836-B183
> Reporter: Radim Hopp
> Assignee: Rob Stryker
> Fix For: 4.3.1.CR1, 4.4.0.Alpha1
>
>
> Removing credentials (which are stored in secure storage) using
> CredentialPreferencePage without being authenticated to secure storage (see steps to reproduce on how to do that) seems to delete the credentials, but after eclipse restart, the credentials are still there. I would prefer message saying something like "Unable to delete credentials stored in secure storage without atuhenticating to secure storage".
--
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 updated JBIDE-21341:
--------------------------------
Fix Version/s: 4.4.0.Alpha1
> 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, 4.4.0.Alpha1
>
> 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-21647) Add EAP 7 Beta to stacks.yaml
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21647?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-21647:
-------------------------------------
Assigned to [~rob.stryker] so he can oordinate with [~rafabene] to make the change upstream (as I can't assign that one directly to Rafa)
> Add EAP 7 Beta to stacks.yaml
> -----------------------------
>
> Key: JBIDE-21647
> URL: https://issues.jboss.org/browse/JBIDE-21647
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: runtime-detection, server
> Reporter: Fred Bricon
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.3.1.CR1
>
>
> EAP 7 should be available from download runtime wizard. This means it should be added to stacks.yaml.
> Adding EAP 7 Beta now is fine. It should be updated to GA once it's released.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21647) Add EAP 7 Beta to stacks.yaml
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21647?page=com.atlassian.jira.plugi... ]
Fred Bricon edited comment on JBIDE-21647 at 2/16/16 9:23 AM:
--------------------------------------------------------------
Assigned to [~rob.stryker] so he can coordinate with [~rafabene] to make the change upstream (as I can't assign that one directly to Rafa)
was (Author: fbricon):
Assigned to [~rob.stryker] so he can oordinate with [~rafabene] to make the change upstream (as I can't assign that one directly to Rafa)
> Add EAP 7 Beta to stacks.yaml
> -----------------------------
>
> Key: JBIDE-21647
> URL: https://issues.jboss.org/browse/JBIDE-21647
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: runtime-detection, server
> Reporter: Fred Bricon
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.3.1.CR1
>
>
> EAP 7 should be available from download runtime wizard. This means it should be added to stacks.yaml.
> Adding EAP 7 Beta now is fine. It should be updated to GA once it's released.
--
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:
-------------------------------------
I remember hitting this bug in the past, but it was inconsistant and only happened some of the time for me. With the patch I am unable to replicate after 8 restarts. I +1.
> 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
> Assignee: Rob Stryker
> Priority: Critical
> 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-21665) Scaling OS3 application does not work properly
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21665?page=com.atlassian.jira.plugi... ]
Jeff Cantrill commented on JBIDE-21665:
---------------------------------------
[~maxandersen] case #2 is the one I dont know how to handle. I dont know how to detect the user changed the content but not saved.
> Scaling OS3 application does not work properly
> ----------------------------------------------
>
> Key: JBIDE-21665
> URL: https://issues.jboss.org/browse/JBIDE-21665
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Jeff Cantrill
> Priority: Critical
> Labels: openshift_v3
> Attachments: edit_error.png
>
>
> When I am trying to scale application via tooling, first attempt to set replicas amount works but every consecutive attempt to edit same resource fails. See following screenshot of the error followed by stack trace
> !edit_error.png!
> {code}
> com.openshift.restclient.OpenShiftException: Could not update resource eap-app-1: {
> "kind": "Status",
> "apiVersion": "v1",
> "metadata": {},
> "status": "Failure",
> "message": "replicationControllers \"eap-app-1\" cannot be updated: the object has been modified; please apply your changes to the latest version and try again",
> "reason": "Conflict",
> "details": {
> "name": "eap-app-1",
> "kind": "replicationControllers"
> },
> "code": 409
> }
> at com.openshift.internal.restclient.DefaultClient.createOpenShiftException(DefaultClient.java:480)
> at com.openshift.internal.restclient.DefaultClient.update(DefaultClient.java:247)
> at org.jboss.tools.openshift.internal.ui.property.OpenShiftResourceDocumentProvider$2.run(OpenShiftResourceDocumentProvider.java:92)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: com.openshift.internal.restclient.http.HttpClientException: {
> "kind": "Status",
> "apiVersion": "v1",
> "metadata": {},
> "status": "Failure",
> "message": "replicationControllers \"eap-app-1\" cannot be updated: the object has been modified; please apply your changes to the latest version and try again",
> "reason": "Conflict",
> "details": {
> "name": "eap-app-1",
> "kind": "replicationControllers"
> },
> "code": 409
> }
> at com.openshift.internal.restclient.http.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:226)
> at com.openshift.internal.restclient.http.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:191)
> at com.openshift.internal.restclient.http.UrlConnectionHttpClient.put(UrlConnectionHttpClient.java:119)
> at com.openshift.internal.restclient.DefaultClient.update(DefaultClient.java:243)
> ... 2 more
> Caused by: java.io.IOException: Server returned HTTP response code: 409 for URL: https://10.1.2.2:8443/api/v1/namespaces/project01/replicationcontrollers/...
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1840)
> 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:187)
> ... 4 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21662) Server adapter: workspace project is not automatically published if there was no initial publish
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21662?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-21662:
------------------------------------------
I still believe that this unexpected requirement is not critical but an annoyance worth Major priority, not Minor
> Server adapter: workspace project is not automatically published if there was no initial publish
> ------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21662
> URL: https://issues.jboss.org/browse/JBIDE-21662
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Rob Stryker
> Labels: openshift_v3, server_adapter
> Fix For: 4.3.1.CR1
>
>
> When I am having a workspace project, OS3 application and server adapter, application should be automatically changed based on local file disk changes as it was introduced in JBIDE-21371. But auto-publish does not work if there was not performed initial publish on server adapter which links workspace project with OS 3 application.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month