[JBoss JIRA] (JBIDE-20797) CCE on first start on clean install of CR1
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20797?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-20797:
---------------------------------------
Now the question is how to verify the fix, since I never saw the original problem in the first place. [~vrubezhny], any idea?
> CCE on first start on clean install of CR1
> ------------------------------------------
>
> Key: JBIDE-20797
> URL: https://issues.jboss.org/browse/JBIDE-20797
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: upstream
> Affects Versions: 4.3.0.CR1
> Reporter: Max Rydahl Andersen
> Assignee: Victor Rubezhny
> Fix For: 4.3.1.Beta2, 4.4.0.Alpha1
>
>
> clean install of eclipse JEE + CR1 jbosstools for mars.
> Get this error on startup on a clean workspace:
> {code}
> java.lang.ClassCastException: [Lorg.eclipse.swt.graphics.FontData; cannot be cast to java.lang.String
> at org.eclipse.ui.internal.themes.Theme$1.propertyChange(Theme.java:124)
> at org.eclipse.ui.preferences.ScopedPreferenceStore$3.run(ScopedPreferenceStore.java:351)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.preferences.ScopedPreferenceStore.firePropertyChangeEvent(ScopedPreferenceStore.java:347)
> at org.eclipse.jface.preference.PreferenceConverter.setValue(PreferenceConverter.java:463)
> at org.eclipse.wst.jsdt.internal.ui.JavaScriptPlugin.ensurePreferenceStoreBackwardsCompatibility(JavaScriptPlugin.java:395)
> at org.eclipse.wst.jsdt.internal.ui.JavaScriptPlugin.start(JavaScriptPlugin.java:336)
> at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:771)
> at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:1)
> at java.security.AccessController.doPrivileged(Native Method)
> at org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:764)
> at org.eclipse.osgi.internal.framework.BundleContextImpl.start(BundleContextImpl.java:721)
> at org.eclipse.osgi.internal.framework.EquinoxBundle.startWorker0(EquinoxBundle.java:941)
> at org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.startWorker(EquinoxBundle.java:318)
> at org.eclipse.osgi.container.Module.doStart(Module.java:571)
> at org.eclipse.osgi.container.Module.start(Module.java:439)
> at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:454)
> at org.eclipse.osgi.internal.hooks.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:107)
> at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findLocalClass(ClasspathManager.java:531)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.findLocalClass(ModuleClassLoader.java:324)
> at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:327)
> at org.eclipse.osgi.internal.loader.sources.SingleSourcePackage.loadClass(SingleSourcePackage.java:36)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:398)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:352)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:344)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:160)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at tern.eclipse.ide.jsdt.internal.ui.JavaEditorTracker.editorOpened(JavaEditorTracker.java:157)
> at tern.eclipse.ide.jsdt.internal.ui.JavaEditorTracker.partOpened(JavaEditorTracker.java:152)
> at org.eclipse.ui.internal.WorkbenchPage$18.run(WorkbenchPage.java:4939)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.WorkbenchPage.firePartOpened(WorkbenchPage.java:4936)
> at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart$2.handleEvent(CompatibilityPart.java:121)
> at org.eclipse.e4.ui.services.internal.events.UIEventHandler$1.run(UIEventHandler.java:40)
> at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:186)
> at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:145)
> at org.eclipse.swt.widgets.Display.syncExec(Display.java:4781)
> at org.eclipse.e4.ui.internal.workbench.swt.E4Application$1.syncExec(E4Application.java:211)
> at org.eclipse.e4.ui.services.internal.events.UIEventHandler.handleEvent(UIEventHandler.java:36)
> at org.eclipse.equinox.internal.event.EventHandlerWrapper.handleEvent(EventHandlerWrapper.java:197)
> at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:197)
> at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:1)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
> at org.eclipse.equinox.internal.event.EventAdminImpl.dispatchEvent(EventAdminImpl.java:135)
> at org.eclipse.equinox.internal.event.EventAdminImpl.sendEvent(EventAdminImpl.java:78)
> at org.eclipse.equinox.internal.event.EventComponent.sendEvent(EventComponent.java:39)
> at org.eclipse.e4.ui.services.internal.events.EventBroker.send(EventBroker.java:85)
> at org.eclipse.e4.ui.internal.workbench.UIEventPublisher.notifyChanged(UIEventPublisher.java:59)
> at org.eclipse.emf.common.notify.impl.BasicNotifierImpl.eNotify(BasicNotifierImpl.java:374)
> at org.eclipse.e4.ui.model.application.ui.basic.impl.PartImpl.setObject(PartImpl.java:410)
> at org.eclipse.e4.ui.workbench.renderers.swt.ContributedPartRenderer.createWidget(ContributedPartRenderer.java:131)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createWidget(PartRenderingEngine.java:971)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:640)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:746)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$0(PartRenderingEngine.java:717)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$2.run(PartRenderingEngine.java:711)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:695)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl$1.handleEvent(PartServiceImpl.java:99)
> at org.eclipse.e4.ui.services.internal.events.UIEventHandler$1.run(UIEventHandler.java:40)
> at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:186)
> at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:145)
> at org.eclipse.swt.widgets.Display.syncExec(Display.java:4781)
> at org.eclipse.e4.ui.internal.workbench.swt.E4Application$1.syncExec(E4Application.java:211)
> at org.eclipse.e4.ui.services.internal.events.UIEventHandler.handleEvent(UIEventHandler.java:36)
> at org.eclipse.equinox.internal.event.EventHandlerWrapper.handleEvent(EventHandlerWrapper.java:197)
> at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:197)
> at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:1)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
> at org.eclipse.equinox.internal.event.EventAdminImpl.dispatchEvent(EventAdminImpl.java:135)
> at org.eclipse.equinox.internal.event.EventAdminImpl.sendEvent(EventAdminImpl.java:78)
> at org.eclipse.equinox.internal.event.EventComponent.sendEvent(EventComponent.java:39)
> at org.eclipse.e4.ui.services.internal.events.EventBroker.send(EventBroker.java:85)
> at org.eclipse.e4.ui.internal.workbench.UIEventPublisher.notifyChanged(UIEventPublisher.java:59)
> at org.eclipse.emf.common.notify.impl.BasicNotifierImpl.eNotify(BasicNotifierImpl.java:374)
> at org.eclipse.e4.ui.model.application.ui.impl.ElementContainerImpl.setSelectedElement(ElementContainerImpl.java:171)
> at org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.showElementInWindow(ModelServiceImpl.java:494)
> at org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.bringToTop(ModelServiceImpl.java:458)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.delegateBringToTop(PartServiceImpl.java:724)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.bringToTop(PartServiceImpl.java:396)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.showPart(PartServiceImpl.java:1166)
> at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:3234)
> at org.eclipse.ui.internal.WorkbenchPage.access$25(WorkbenchPage.java:3149)
> at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:3131)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3126)
> at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3090)
> at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3071)
> at org.jboss.tools.central.JBossCentralActivator.openJBossCentralEditor(JBossCentralActivator.java:436)
> at org.jboss.tools.central.JBossCentralActivator$6$1.run(JBossCentralActivator.java:411)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4024)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3700)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
> 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:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> 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:483)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21495) For JBIDE 4.3.1.Beta2: Code Freeze + Branch [Integration Tests]
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21495?page=com.atlassian.jira.plugi... ]
Pavol Srna closed JBIDE-21495.
------------------------------
> For JBIDE 4.3.1.Beta2: Code Freeze + Branch [Integration Tests]
> ---------------------------------------------------------------
>
> Key: JBIDE-21495
> URL: https://issues.jboss.org/browse/JBIDE-21495
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: qa
> Reporter: Nick Boldt
> Assignee: Pavol Srna
> Priority: Blocker
> Labels: task
> Fix For: 4.3.1.Beta2
>
>
> For JBIDE 4.3.1.Beta2 [Integration Tests]: Please perform the following tasks:
> 0. If nothing has changed in your component since the release of JBoss Tools 4.3.0.Final (eg., Portal, Freemarker?), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.1.Beta2
> [Unresolved JIRAs with fixVersion = 4.3.1.Beta2, 9.1.0.Beta2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...]
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.3.1, 1.2.3 to 1.2.100, or 2.3.100 to 2.3.101
> *NOTE:* If you already did this earlier when we were preparing for Beta2 (after 4.3.0.Final was released), you do *not* need to do so again.
> Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.3.x branch.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.24.0:set-version -DnewVersion=4.3.1-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.3.1.Beta2-SNAPSHOT.
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.1.Beta2-SNAPSHOT</version>
> </parent>
> {code}
> 3a. Ensure you've *built your code* using the latest *minimum* target platform version 4.50.2.Beta2-SNAPSHOT (4.50 = Eclipse Mars.0)
> {code}
> mvn clean verify -Dtpc.version=4.50.2.Beta2-SNAPSHOT
> {code}
> 3b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.52.0.Beta2-SNAPSHOT (4.52 = Eclipse Mars.2)
> {code}
> mvn clean verify -Dtpc.version=4.52.0.Beta2-SNAPSHOT
> {code}
> 4. Branch from your existing jbosstools-4.3.x branch into a new *{color:blue}jbosstools-4.3.1.Beta2x{color}* branch;
> {code}
> git checkout jbosstools-4.3.x
> git pull origin jbosstools-4.3.x
> git checkout -b jbosstools-4.3.1.Beta2x
> git push origin jbosstools-4.3.1.Beta2x
> {code}
> 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}jbosstools-4.3.x branch{color}*.
> {code}
> git checkout jbosstools-4.3.x
> git pull origin jbosstools-4.3.x
> {code}
> 6. Update your *{color:orange}jbosstools-4.3.x branch{color}* parent pom to use the latest version, *{color:orange}4.3.1.CR1-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.1.CR1-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:blue}4.3.1.Beta2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.1.Beta2x{color}* branch, and
> * *{color:orange}4.3.1.CR1-SNAPSHOT{color}* in your *{color:orange}jbosstools-4.3.x{color}* branch.
> 7. Close (do not resolve) this JIRA when done.
> 8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Integration Tests task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21495) For JBIDE 4.3.1.Beta2: Code Freeze + Branch [Integration Tests]
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21495?page=com.atlassian.jira.plugi... ]
Pavol Srna resolved JBIDE-21495.
--------------------------------
Resolution: Done
I've created jbosstools-4.3.1.Beta2x branch.
> For JBIDE 4.3.1.Beta2: Code Freeze + Branch [Integration Tests]
> ---------------------------------------------------------------
>
> Key: JBIDE-21495
> URL: https://issues.jboss.org/browse/JBIDE-21495
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: qa
> Reporter: Nick Boldt
> Assignee: Pavol Srna
> Priority: Blocker
> Labels: task
> Fix For: 4.3.1.Beta2
>
>
> For JBIDE 4.3.1.Beta2 [Integration Tests]: Please perform the following tasks:
> 0. If nothing has changed in your component since the release of JBoss Tools 4.3.0.Final (eg., Portal, Freemarker?), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.1.Beta2
> [Unresolved JIRAs with fixVersion = 4.3.1.Beta2, 9.1.0.Beta2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...]
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.3.1, 1.2.3 to 1.2.100, or 2.3.100 to 2.3.101
> *NOTE:* If you already did this earlier when we were preparing for Beta2 (after 4.3.0.Final was released), you do *not* need to do so again.
> Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.3.x branch.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.24.0:set-version -DnewVersion=4.3.1-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.3.1.Beta2-SNAPSHOT.
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.1.Beta2-SNAPSHOT</version>
> </parent>
> {code}
> 3a. Ensure you've *built your code* using the latest *minimum* target platform version 4.50.2.Beta2-SNAPSHOT (4.50 = Eclipse Mars.0)
> {code}
> mvn clean verify -Dtpc.version=4.50.2.Beta2-SNAPSHOT
> {code}
> 3b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.52.0.Beta2-SNAPSHOT (4.52 = Eclipse Mars.2)
> {code}
> mvn clean verify -Dtpc.version=4.52.0.Beta2-SNAPSHOT
> {code}
> 4. Branch from your existing jbosstools-4.3.x branch into a new *{color:blue}jbosstools-4.3.1.Beta2x{color}* branch;
> {code}
> git checkout jbosstools-4.3.x
> git pull origin jbosstools-4.3.x
> git checkout -b jbosstools-4.3.1.Beta2x
> git push origin jbosstools-4.3.1.Beta2x
> {code}
> 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}jbosstools-4.3.x branch{color}*.
> {code}
> git checkout jbosstools-4.3.x
> git pull origin jbosstools-4.3.x
> {code}
> 6. Update your *{color:orange}jbosstools-4.3.x branch{color}* parent pom to use the latest version, *{color:orange}4.3.1.CR1-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.1.CR1-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:blue}4.3.1.Beta2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.1.Beta2x{color}* branch, and
> * *{color:orange}4.3.1.CR1-SNAPSHOT{color}* in your *{color:orange}jbosstools-4.3.x{color}* branch.
> 7. Close (do not resolve) this JIRA when done.
> 8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Integration Tests task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21518) CoreException when validating wrong credentials (Unknown response code: 503)
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21518?page=com.atlassian.jira.plugi... ]
Radim Hopp commented on JBIDE-21518:
------------------------------------
Everything is as expected using Beta1, so it probably isn't related to JBIDE-21514...
> CoreException when validating wrong credentials (Unknown response code: 503)
> ----------------------------------------------------------------------------
>
> Key: JBIDE-21518
> URL: https://issues.jboss.org/browse/JBIDE-21518
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common/jst/core, runtime-detection
> Affects Versions: 4.3.1.Beta2
> Environment: JBDS 9.1.0.Beta2-v20160121-0657-B250
> Reporter: Radim Hopp
>
> Validating wrong credentials in DownloadRuntime wizard throws "An error occurred while validating your credentials. org.eclipse.core.runtime.CoreException - Unknown response code: 503"
> {noformat:title=ErrorLog}
> org.eclipse.core.runtime.CoreException: Unknown response code: 503
> at org.jboss.tools.runtime.ui.internal.wizard.workflow.DownloadManagerWorkflowUtility.getWorkflowStatus(DownloadManagerWorkflowUtility.java:58)
> at org.jboss.tools.runtime.ui.internal.wizard.workflow.DownloadManagerCredentialsFragment.validateCredentials(DownloadManagerCredentialsFragment.java:205)
> at org.jboss.tools.runtime.ui.internal.wizard.workflow.DownloadManagerCredentialsFragment.access$1(DownloadManagerCredentialsFragment.java:203)
> at org.jboss.tools.runtime.ui.internal.wizard.workflow.DownloadManagerCredentialsFragment$3.run(DownloadManagerCredentialsFragment.java:168)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119)
> {noformat}
> My blind guess is that it's relevant to https://issues.jboss.org/browse/JBIDE-21514, because I think, that correct message was displayed yesterday when one used wrong credentials.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21518) CoreException when validating wrong credentials (Unknown response code: 503)
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21518?page=com.atlassian.jira.plugi... ]
Radim Hopp updated JBIDE-21518:
-------------------------------
Affects Version/s: 4.3.1.Beta2
> CoreException when validating wrong credentials (Unknown response code: 503)
> ----------------------------------------------------------------------------
>
> Key: JBIDE-21518
> URL: https://issues.jboss.org/browse/JBIDE-21518
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common/jst/core, runtime-detection
> Affects Versions: 4.3.1.Beta2
> Environment: JBDS 9.1.0.Beta2-v20160121-0657-B250
> Reporter: Radim Hopp
>
> Validating wrong credentials in DownloadRuntime wizard throws "An error occurred while validating your credentials. org.eclipse.core.runtime.CoreException - Unknown response code: 503"
> {noformat:title=ErrorLog}
> org.eclipse.core.runtime.CoreException: Unknown response code: 503
> at org.jboss.tools.runtime.ui.internal.wizard.workflow.DownloadManagerWorkflowUtility.getWorkflowStatus(DownloadManagerWorkflowUtility.java:58)
> at org.jboss.tools.runtime.ui.internal.wizard.workflow.DownloadManagerCredentialsFragment.validateCredentials(DownloadManagerCredentialsFragment.java:205)
> at org.jboss.tools.runtime.ui.internal.wizard.workflow.DownloadManagerCredentialsFragment.access$1(DownloadManagerCredentialsFragment.java:203)
> at org.jboss.tools.runtime.ui.internal.wizard.workflow.DownloadManagerCredentialsFragment$3.run(DownloadManagerCredentialsFragment.java:168)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119)
> {noformat}
> My blind guess is that it's relevant to https://issues.jboss.org/browse/JBIDE-21514, because I think, that correct message was displayed yesterday when one used wrong credentials.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21518) CoreException when validating wrong credentials (Unknown response code: 503)
by Radim Hopp (JIRA)
Radim Hopp created JBIDE-21518:
----------------------------------
Summary: CoreException when validating wrong credentials (Unknown response code: 503)
Key: JBIDE-21518
URL: https://issues.jboss.org/browse/JBIDE-21518
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: common/jst/core, runtime-detection
Environment: JBDS 9.1.0.Beta2-v20160121-0657-B250
Reporter: Radim Hopp
Validating wrong credentials in DownloadRuntime wizard throws "An error occurred while validating your credentials. org.eclipse.core.runtime.CoreException - Unknown response code: 503"
{noformat:title=ErrorLog}
org.eclipse.core.runtime.CoreException: Unknown response code: 503
at org.jboss.tools.runtime.ui.internal.wizard.workflow.DownloadManagerWorkflowUtility.getWorkflowStatus(DownloadManagerWorkflowUtility.java:58)
at org.jboss.tools.runtime.ui.internal.wizard.workflow.DownloadManagerCredentialsFragment.validateCredentials(DownloadManagerCredentialsFragment.java:205)
at org.jboss.tools.runtime.ui.internal.wizard.workflow.DownloadManagerCredentialsFragment.access$1(DownloadManagerCredentialsFragment.java:203)
at org.jboss.tools.runtime.ui.internal.wizard.workflow.DownloadManagerCredentialsFragment$3.run(DownloadManagerCredentialsFragment.java:168)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119)
{noformat}
My blind guess is that it's relevant to https://issues.jboss.org/browse/JBIDE-21514, because I think, that correct message was displayed yesterday when one used wrong credentials.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
