[JBoss JIRA] (JBIDE-26532) Connection wizard: token is not updated after pasting login command with same server
by Andre Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26532?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-26532:
-------------------------------------
Steps to Reproduce:
1. Open Connection wizard
2. Have a command in clipboard:
{code:java}
oc login https://api.starter-us-east-2.openshift.com --token=12345_67890
{code}
3. command is correctly parsed
4. Copy on clipboard login command with same server, but different token, e.g.:
{code:java}
oc login https://api.starter-us-east-2.openshift.com --token=12345_67890123456
{code}
5. Result: token is not updated.
Expected: token is updated.
Second test case: Use paste login command button in wizard
1. Logged into openshift web console
2. Copy login command into clipboard
3. Open devstudio -> Open OS explorer
4. Click New connection (as I did not have any)
5. Wizard is opened and login command copied from clipborad - pass
6. Remove all credentials, have empty wizard
7. Click paste login comm. button
8. Assert: Credentials are pasted
Actual result: Failed, button does not work, if I switch between oauth and basic authentication, token gets filled in, but not a server. Button seems not to be working correctly, although, I managed to actually use the button correctly and paste an information there, but cannot repeat it...
was:
1. Open Connection wizard
2. Have a command in clipboard:
{code:java}
oc login https://api.starter-us-east-2.openshift.com --token=12345_67890
{code}
3. command is correctly parsed
4. Copy on clipboard login command with same server, but different token, e.g.:
{code:java}
oc login https://api.starter-us-east-2.openshift.com --token=12345_67890123456
{code}
5. Result: token is not updated.
Expected: token is updated.
> Connection wizard: token is not updated after pasting login command with same server
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-26532
> URL: https://issues.jboss.org/browse/JBIDE-26532
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.11.0.AM1
> Reporter: Josef Kopriva
> Assignee: Josef Kopriva
> Priority: Major
> Fix For: 4.11.0.AM1
>
>
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (JBIDE-26117) Connection Wizard: Parse Login command (that was copied to clipboard by the web-ui)
by Andre Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26117?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-26117:
------------------------------------------
[~jkopriva] +1, thx
> Connection Wizard: Parse Login command (that was copied to clipboard by the web-ui)
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-26117
> URL: https://issues.jboss.org/browse/JBIDE-26117
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.6.0.Final
> Reporter: Josef Kopriva
> Assignee: Josef Kopriva
> Priority: Major
> Labels: connection_wizard
> Fix For: 4.11.0.AM1
>
>
> The OpenShift web-ui provides a menu entry that creates the oc login command in your local clipboard: https://stackoverflow.com/questions/49548380/cannot-find-openshift-3-logi...
> Currently, Eclipse users would have to paste it to some notepad and use the info in it to manually create a connection. The tooling could facilitate this by parsing the clipboard and creating a connection:
> The Eclipse
> There could be a button for parsing login command in clipboard.
> Steps:
> 1. User logins in web browser in OpenShift Console.
> 2. User clicks on "Copy Login Command"
> 3. In OpenShift tooling there could be button for parse login command from clipboard.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (JBIDE-26541) Mylyn: refresh builds does not work under JDK11
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-26541?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-26541:
-------------------------------
Fix Version/s: 4.11.0.Final
> Mylyn: refresh builds does not work under JDK11
> -----------------------------------------------
>
> Key: JBIDE-26541
> URL: https://issues.jboss.org/browse/JBIDE-26541
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform, upstream
> Affects Versions: 4.11.0.AM1
> Environment: F29 + JDK11
> Reporter: Josef Kopriva
> Priority: Major
> Fix For: 4.11.0.Final
>
>
> Message from error log:
> {code:java}
> eclipse.buildId=12.11.0.AM1-v20190128-0120-B3931
> java.version=11.0.1
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -data file:/home/jkopriva/git/workspace-spring/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> org.eclipse.mylyn.commons.repositories.ui
> Error
> Fri Feb 01 14:33:04 CET 2019
> Unexpected error during repository validation.
> java.lang.reflect.InvocationTargetException
> at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:401)
> at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:977)
> at org.eclipse.mylyn.commons.ui.dialogs.EnhancedWizardDialog.run(EnhancedWizardDialog.java:138)
> at org.eclipse.mylyn.commons.repositories.ui.RepositoryWizardPage.run(RepositoryWizardPage.java:98)
> at org.eclipse.mylyn.commons.repositories.ui.RepositoryLocationPart.validate(RepositoryLocationPart.java:554)
> at org.eclipse.mylyn.builds.ui.spi.BuildServerPart$1.widgetSelected(BuildServerPart.java:180)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:252)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:89)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5663)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1386)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4931)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4472)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:822)
> at org.eclipse.jface.window.Window.open(Window.java:798)
> at org.eclipse.mylyn.commons.repositories.ui.RepositoryUi.openNewRepositoryDialog(RepositoryUi.java:90)
> at org.eclipse.mylyn.internal.builds.ui.view.NewBuildServerAction.run(NewBuildServerAction.java:35)
> at org.eclipse.mylyn.internal.builds.ui.view.BuildsView$2.widgetSelected(BuildsView.java:326)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:252)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:89)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5663)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1386)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1412)
> at org.eclipse.swt.widgets.Widget.sendSelectionEvent(Widget.java:1526)
> at org.eclipse.swt.widgets.Link.gtk_button_release_event(Link.java:387)
> at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:1946)
> at org.eclipse.swt.widgets.Control.windowProc(Control.java:6298)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:5880)
> at org.eclipse.swt.internal.gtk.GTK._gtk_main_do_event(Native Method)
> at org.eclipse.swt.internal.gtk.GTK.gtk_main_do_event(GTK.java:3969)
> at org.eclipse.swt.widgets.Display.eventProc(Display.java:1385)
> at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method)
> at org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:1581)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4470)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1173)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:339)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1062)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:636)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:339)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:563)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:151)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:155)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:203)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:137)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:107)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:255)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:659)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:595)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1501)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1474)
> Caused by: java.lang.NoClassDefFoundError: javax/xml/bind/JAXBException
> at org.eclipse.mylyn.internal.hudson.core.client.RestfulHudsonClient.validate(RestfulHudsonClient.java:463)
> at org.eclipse.mylyn.internal.hudson.core.HudsonServerBehaviour.validate(HudsonServerBehaviour.java:956)
> at org.eclipse.mylyn.builds.internal.core.BuildServer.validate(BuildServer.java:369)
> at org.eclipse.mylyn.builds.ui.spi.BuildServerPart$Validator.run(BuildServerPart.java:114)
> at org.eclipse.mylyn.commons.repositories.ui.RepositoryLocationPart$2.run(RepositoryLocationPart.java:558)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122)
> Caused by: java.lang.ClassNotFoundException: javax.xml.bind.JAXBException cannot be found by org.eclipse.mylyn.hudson.core_1.16.0.v20180403-2055
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:511)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:422)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:414)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:153)
> at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
> ... 6 more
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (JBIDE-26117) Connection Wizard: Parse Login command (that was copied to clipboard by the web-ui)
by Andre Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26117?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-26117:
------------------------------------------
[~jkopriva] dare to address the issues that [~odockal] found? I guess that we should create a new jira?
> Connection Wizard: Parse Login command (that was copied to clipboard by the web-ui)
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-26117
> URL: https://issues.jboss.org/browse/JBIDE-26117
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.6.0.Final
> Reporter: Josef Kopriva
> Assignee: Josef Kopriva
> Priority: Major
> Labels: connection_wizard
> Fix For: 4.11.0.AM1
>
>
> The OpenShift web-ui provides a menu entry that creates the oc login command in your local clipboard: https://stackoverflow.com/questions/49548380/cannot-find-openshift-3-logi...
> Currently, Eclipse users would have to paste it to some notepad and use the info in it to manually create a connection. The tooling could facilitate this by parsing the clipboard and creating a connection:
> The Eclipse
> There could be a button for parsing login command in clipboard.
> Steps:
> 1. User logins in web browser in OpenShift Console.
> 2. User clicks on "Copy Login Command"
> 3. In OpenShift tooling there could be button for parse login command from clipboard.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (JBIDE-26520) Create automated RHDS Launcher Application tests
by Zbyněk Červinka (Jira)
[ https://issues.jboss.org/browse/JBIDE-26520?page=com.atlassian.jira.plugi... ]
Zbyněk Červinka closed JBIDE-26520.
-----------------------------------
Resolution: Done
> Create automated RHDS Launcher Application tests
> ------------------------------------------------
>
> Key: JBIDE-26520
> URL: https://issues.jboss.org/browse/JBIDE-26520
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: central
> Affects Versions: 4.10.0.AM1
> Environment: Same as central.itests on Jenkins (will be part of central.itests)
> Reporter: Zbyněk Červinka
> Assignee: Zbyněk Červinka
> Priority: Major
> Fix For: 4.11.0.AM1
>
>
> Create automated RHDS Launcher Application tests. Tests will be part of the central.itests and they will cover 4 test cases described in Polarion:
> -> JBDS-9886
> -> JBDS-9887
> -> JBDS-9888
> -> JBDS-9889
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (JBIDE-26520) Create automated RHDS Launcher Application tests
by Zbyněk Červinka (Jira)
[ https://issues.jboss.org/browse/JBIDE-26520?page=com.atlassian.jira.plugi... ]
Zbyněk Červinka updated JBIDE-26520:
------------------------------------
Fix Version/s: 4.11.0.AM1
> Create automated RHDS Launcher Application tests
> ------------------------------------------------
>
> Key: JBIDE-26520
> URL: https://issues.jboss.org/browse/JBIDE-26520
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: central
> Affects Versions: 4.10.0.AM1
> Environment: Same as central.itests on Jenkins (will be part of central.itests)
> Reporter: Zbyněk Červinka
> Assignee: Zbyněk Červinka
> Priority: Major
> Fix For: 4.11.0.AM1
>
>
> Create automated RHDS Launcher Application tests. Tests will be part of the central.itests and they will cover 4 test cases described in Polarion:
> -> JBDS-9886
> -> JBDS-9887
> -> JBDS-9888
> -> JBDS-9889
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (JBIDE-26117) Connection Wizard: Parse Login command (that was copied to clipboard by the web-ui)
by Ondrej Dockal (Jira)
[ https://issues.jboss.org/browse/JBIDE-26117?page=com.atlassian.jira.plugi... ]
Ondrej Dockal commented on JBIDE-26117:
---------------------------------------
First test case: Credentials automatically passed into new connection wizard
1. Logged into openshift web console
2. Copy login command into clipboard
3. Open devstudio -> Open OS explorer
4. Click New connection (as I did not have any)
5. Assert: wizard is opened and login copied from clipborad
6. Assert: Connection is created
Actual result: PASS
Second test case: Use paste login command button in wizard
1. Logged into openshift web console
2. Copy login command into clipboard
3. Open devstudio -> Open OS explorer
4. Click New connection (as I did not have any)
5. Wizard is opened and login command copied from clipborad - pass
6. Remove all credentials, have empty wizard
7. Click paste login comm. button
8. Assert: Credentials are pasted
Actual result: Failed, button does not work, if I switch between oauth and basic authentication, token gets filled in, but not a server. Button seems not to be working correctly, although, I managed to actually use the button correctly and paste an information there, but cannot repeat it...
> Connection Wizard: Parse Login command (that was copied to clipboard by the web-ui)
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-26117
> URL: https://issues.jboss.org/browse/JBIDE-26117
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.6.0.Final
> Reporter: Josef Kopriva
> Assignee: Josef Kopriva
> Priority: Major
> Labels: connection_wizard
> Fix For: 4.11.0.AM1
>
>
> The OpenShift web-ui provides a menu entry that creates the oc login command in your local clipboard: https://stackoverflow.com/questions/49548380/cannot-find-openshift-3-logi...
> Currently, Eclipse users would have to paste it to some notepad and use the info in it to manually create a connection. The tooling could facilitate this by parsing the clipboard and creating a connection:
> The Eclipse
> There could be a button for parsing login command in clipboard.
> Steps:
> 1. User logins in web browser in OpenShift Console.
> 2. User clicks on "Copy Login Command"
> 3. In OpenShift tooling there could be button for parse login command from clipboard.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month