[JBoss JIRA] (JBIDE-21827) If org.jboss.quickstarts.eap is missing, provide quickfix
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-21827:
-----------------------------------
Summary: If org.jboss.quickstarts.eap is missing, provide quickfix
Key: JBIDE-21827
URL: https://issues.jboss.org/browse/JBIDE-21827
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: maven
Affects Versions: 4.3.1.CR1
Reporter: Rob Stryker
When importing kitchensink quickstart, it's possible that the maven redhat repository for "org.jboss.quickstarts.eap" is missing.
A quickfix should be provided to remedy this situation
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21826) install-grinder failing again
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21826?page=com.atlassian.jira.plugi... ]
Nick Boldt reassigned JBIDE-21826:
----------------------------------
Assignee: Mickael Istria
> install-grinder failing again
> -----------------------------
>
> Key: JBIDE-21826
> URL: https://issues.jboss.org/browse/JBIDE-21826
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, install-tests
> Affects Versions: 4.3.1.CR1, 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Fix For: 4.3.1.CR1, 4.4.0.Alpha1
>
> Attachments: central_loaded_no_gtk_installed_javaEE_perspective_testInstall(org.jboss.tools.tests.installation.InstallFromCentralTest).jpeg, central_not_loaded_loading...(2)_javaEE_perspective_testInstall(org.jboss.tools.tests.installation.InstallFromCentralTest).jpeg, central_not_loaded_loading..._javaEE_perspective_testInstall(org.jboss.tools.tests.installation.InstallFromCentralTest).jpeg, central_not_loaded_no_gtk_installed_javaEE_perspective_launchbar_enabled_testInstall(org.jboss.tools.tests.installation.InstallFromCentralTest).jpeg, central_not_loaded_no_gtk_installed_javaEE_perspective_testInstall(org.jboss.tools.tests.installation.InstallFromCentralTest).jpeg, central_not_loaded_no_gtk_installed_Resource_Perspective_testInstall(org.jboss.tools.tests.installation.InstallFromCentralTest).jpeg
>
>
> As of Feb 4, install-grinder was mostly blue, and the occasional red ball was fixed w/ naginator. (See JBIDE-20331)
> But since then, install grinder is failing again in 4.3.1.CR1 and 4.4.0.Alpha1 builds.
> Not sure what's blocking the UI this time, but on the plus side, at least Red Hat Central now reports when GTK2/3 is missing on the slave.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21826) install-grinder failing again
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21826?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-21826:
-------------------------------
Fix Version/s: 4.3.1.CR1
4.4.0.Alpha1
> install-grinder failing again
> -----------------------------
>
> Key: JBIDE-21826
> URL: https://issues.jboss.org/browse/JBIDE-21826
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, install-tests
> Affects Versions: 4.3.1.CR1, 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Fix For: 4.3.1.CR1, 4.4.0.Alpha1
>
> Attachments: central_loaded_no_gtk_installed_javaEE_perspective_testInstall(org.jboss.tools.tests.installation.InstallFromCentralTest).jpeg, central_not_loaded_loading...(2)_javaEE_perspective_testInstall(org.jboss.tools.tests.installation.InstallFromCentralTest).jpeg, central_not_loaded_loading..._javaEE_perspective_testInstall(org.jboss.tools.tests.installation.InstallFromCentralTest).jpeg, central_not_loaded_no_gtk_installed_javaEE_perspective_launchbar_enabled_testInstall(org.jboss.tools.tests.installation.InstallFromCentralTest).jpeg, central_not_loaded_no_gtk_installed_javaEE_perspective_testInstall(org.jboss.tools.tests.installation.InstallFromCentralTest).jpeg, central_not_loaded_no_gtk_installed_Resource_Perspective_testInstall(org.jboss.tools.tests.installation.InstallFromCentralTest).jpeg
>
>
> As of Feb 4, install-grinder was mostly blue, and the occasional red ball was fixed w/ naginator. (See JBIDE-20331)
> But since then, install grinder is failing again in 4.3.1.CR1 and 4.4.0.Alpha1 builds.
> Not sure what's blocking the UI this time, but on the plus side, at least Red Hat Central now reports when GTK2/3 is missing on the slave.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21826) install-grinder failing again
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21826?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-21826:
-------------------------------
Attachment: central_not_loaded_no_gtk_installed_Resource_Perspective_testInstall(org.jboss.tools.tests.installation.InstallFromCentralTest).jpeg
central_not_loaded_no_gtk_installed_javaEE_perspective_testInstall(org.jboss.tools.tests.installation.InstallFromCentralTest).jpeg
central_not_loaded_no_gtk_installed_javaEE_perspective_launchbar_enabled_testInstall(org.jboss.tools.tests.installation.InstallFromCentralTest).jpeg
central_not_loaded_loading..._javaEE_perspective_testInstall(org.jboss.tools.tests.installation.InstallFromCentralTest).jpeg
central_not_loaded_loading...(2)_javaEE_perspective_testInstall(org.jboss.tools.tests.installation.InstallFromCentralTest).jpeg
central_loaded_no_gtk_installed_javaEE_perspective_testInstall(org.jboss.tools.tests.installation.InstallFromCentralTest).jpeg
Some screenshots from recent test failures attached.
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
Collected details:
https://docs.google.com/spreadsheets/d/1OsSTLh5oZZQRDVnOB_6oTW4c20twJoG4D...
> install-grinder failing again
> -----------------------------
>
> Key: JBIDE-21826
> URL: https://issues.jboss.org/browse/JBIDE-21826
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, install-tests
> Affects Versions: 4.3.1.CR1, 4.4.0.Alpha1
> Reporter: Nick Boldt
> Attachments: central_loaded_no_gtk_installed_javaEE_perspective_testInstall(org.jboss.tools.tests.installation.InstallFromCentralTest).jpeg, central_not_loaded_loading...(2)_javaEE_perspective_testInstall(org.jboss.tools.tests.installation.InstallFromCentralTest).jpeg, central_not_loaded_loading..._javaEE_perspective_testInstall(org.jboss.tools.tests.installation.InstallFromCentralTest).jpeg, central_not_loaded_no_gtk_installed_javaEE_perspective_launchbar_enabled_testInstall(org.jboss.tools.tests.installation.InstallFromCentralTest).jpeg, central_not_loaded_no_gtk_installed_javaEE_perspective_testInstall(org.jboss.tools.tests.installation.InstallFromCentralTest).jpeg, central_not_loaded_no_gtk_installed_Resource_Perspective_testInstall(org.jboss.tools.tests.installation.InstallFromCentralTest).jpeg
>
>
> As of Feb 4, install-grinder was mostly blue, and the occasional red ball was fixed w/ naginator. (See JBIDE-20331)
> But since then, install grinder is failing again in 4.3.1.CR1 and 4.4.0.Alpha1 builds.
> Not sure what's blocking the UI this time, but on the plus side, at least Red Hat Central now reports when GTK2/3 is missing on the slave.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21826) install-grinder failing again
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21826?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-21826:
-------------------------------
Description:
As of Feb 4, install-grinder was mostly blue, and the occasional red ball was fixed w/ naginator. (See JBIDE-20331)
But since then, install grinder is failing again in 4.3.1.CR1 and 4.4.0.Alpha1 builds.
Not sure what's blocking the UI this time, but on the plus side, at least Red Hat Central now reports when GTK2/3 is missing on the slave.
was:
Install grinder is failing again in 4.3.1.CR1 and 4.4.0.Alpha1 builds.
Not sure what's blocking the UI this time, but on the plus side, at least Red Hat Central now reports when GTK2/3 is missing on the slave.
> install-grinder failing again
> -----------------------------
>
> Key: JBIDE-21826
> URL: https://issues.jboss.org/browse/JBIDE-21826
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, install-tests
> Affects Versions: 4.3.1.CR1, 4.4.0.Alpha1
> Reporter: Nick Boldt
>
> As of Feb 4, install-grinder was mostly blue, and the occasional red ball was fixed w/ naginator. (See JBIDE-20331)
> But since then, install grinder is failing again in 4.3.1.CR1 and 4.4.0.Alpha1 builds.
> Not sure what's blocking the UI this time, but on the plus side, at least Red Hat Central now reports when GTK2/3 is missing on the slave.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21817) Connection dialog: User is stuck by Sign In triggered via OpenShift 2 server adapter
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21817?page=com.atlassian.jira.plugi... ]
Fred Bricon reassigned JBIDE-21817:
-----------------------------------
Assignee: Viacheslav Kabanovich
Resolution: Done
PR works as advertised.
Applied in master / 4.3.x
Thanks [~scabanovich]!
> Connection dialog: User is stuck by Sign In triggered via OpenShift 2 server adapter
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-21817
> URL: https://issues.jboss.org/browse/JBIDE-21817
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Labels: openshift_v2
> Fix For: 4.3.1.CR1
>
> Attachments: jstack.txt, LockAtStart.png
>
>
> 1. Close Eclipse with
> - Server Editor for OpenShift 2 server adapter open;
> - password for an Opebshift 2 connection not saved in the secure storage;
> - OpenShift Explorer active (maybe not important).
> 2. Open Eclipse - Sign In to OpenShift wizard appears while the application window remains only partially loaded (see screenshot). Once this is reproduced, it is reproduced at each Eclipse start.
> 3. Enter password and finish.
> 4. Progress appears but job does not start (I checked it in debugger) - ui jobs are locked.
> 5. Only red button cancelling connection is active, press it, wizard is unlocked (null pointer exception is fixed in JBIDE-21707).
> 6. Press Cancel, wizard is closed, Application window completes loading. - That
> 7. Connection may be established by Refresh action.
> Stack trace that calls Sign In to Openshift wizard before main window is loaded, it shows that call is initiated by loading Server Editor:
> {code}
> Thread [main] (Suspended (breakpoint at line 274 in Window))
> WizardDialog(Window).<init>(IShellProvider) line: 274
> WizardDialog(Dialog).<init>(IShellProvider) line: 438
> WizardDialog(Dialog).<init>(Shell) line: 419
> WizardDialog(TrayDialog).<init>(Shell) line: 138
> WizardDialog(TitleAreaDialog).<init>(Shell) line: 130
> WizardDialog.<init>(Shell, IWizard) line: 308
> WizardUtils.openWizardDialog(IWizard, Shell) line: 242
> CredentialsPrompter$1.run() line: 44
> UISynchronizer(Synchronizer).syncExec(Runnable) line: 186
> UISynchronizer.syncExec(Runnable) line: 145
> Display.syncExec(Runnable) line: 4634
> CredentialsPrompter.promptAndAuthenticate(IConnection, Object) line: 33
> LazyCredentialsPrompter.promptAndAuthenticate(IConnection, Object) line: 39
> ExpressConnection.promptForCredentials() line: 284
> ExpressConnection.createUser() line: 218
> ExpressConnection.connect() line: 198
> ExpressServerUtils.getApplication(IServerAttributes) line: 161
> ExpressServerUtils.getDeployFolder(IServerAttributes) line: 251
> ExpressServerEditorSection.initWidgets() line: 117
> ExpressServerEditorSection.createSection(Composite) line: 100
> OverviewEditorPart(ServerEditorPart).insertSections(Composite, String) line: 327
> OverviewEditorPart.createPartControl(Composite) line: 279
> ServerEditor(MultiPageEditorPart).addPage(int, IEditorPart, IEditorInput) line: 244
> ServerEditor(MultiPageEditorPart).addPage(IEditorPart, IEditorInput) line: 214
> ServerEditor.createPages() line: 247
> ServerEditor(MultiPageEditorPart).createPartControl(Composite) line: 363
> CompatibilityEditor(CompatibilityPart).createPartControl(IWorkbenchPart, Composite) line: 151
> CompatibilityEditor.createPartControl(IWorkbenchPart, Composite) line: 99
> CompatibilityEditor(CompatibilityPart).create() line: 341
> NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native method]
> NativeMethodAccessorImpl.invoke(Object, Object[]) line: 62
> DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 43
> Method.invoke(Object, Object...) line: 498
> MethodRequestor.execute() line: 56
> InjectorImpl.processAnnotated(Class<Annotation>, Object, Class<?>, PrimaryObjectSupplier, PrimaryObjectSupplier, ArrayList<Class<?>>) line: 925
> InjectorImpl.processAnnotated(Class<Annotation>, Object, Class<?>, PrimaryObjectSupplier, PrimaryObjectSupplier, ArrayList<Class<?>>) line: 906
> InjectorImpl.inject(Object, PrimaryObjectSupplier, PrimaryObjectSupplier) line: 148
> InjectorImpl.internalMake(Class<?>, PrimaryObjectSupplier, PrimaryObjectSupplier) line: 372
> InjectorImpl.make(Class<T>, PrimaryObjectSupplier) line: 291
> ContextInjectionFactory.make(Class<T>, IEclipseContext) line: 162
> ReflectionContributionFactory.createFromBundle(Bundle, IEclipseContext, IEclipseContext, URI) line: 105
> ReflectionContributionFactory.doCreate(String, IEclipseContext, IEclipseContext) line: 74
> ReflectionContributionFactory.create(String, IEclipseContext) line: 56
> ContributedPartRenderer.createWidget(MUIElement, Object) line: 129
> PartRenderingEngine.createWidget(MUIElement, Object) line: 976
> PartRenderingEngine.safeCreateGui(MUIElement, Object, IEclipseContext) line: 652
> PartRenderingEngine.safeCreateGui(MUIElement) line: 758
> PartRenderingEngine.access$0(PartRenderingEngine, MUIElement) line: 729
> PartRenderingEngine$2.run() line: 723
> SafeRunner.run(ISafeRunnable) line: 42
> PartRenderingEngine.createGui(MUIElement) line: 707
> StackRenderer.showTab(MUIElement) line: 1306
> StackRenderer(LazyStackRenderer).postProcess(MUIElement) line: 103
> PartRenderingEngine.safeCreateGui(MUIElement, Object, IEclipseContext) line: 670
> PartRenderingEngine.safeCreateGui(MUIElement) line: 758
> PartRenderingEngine.access$0(PartRenderingEngine, MUIElement) line: 729
> PartRenderingEngine$2.run() line: 723
> SafeRunner.run(ISafeRunnable) line: 42
> PartRenderingEngine.createGui(MUIElement) line: 707
> AreaRenderer(SWTPartRenderer).processContents(MElementContainer<MUIElement>) line: 72
> PartRenderingEngine.safeCreateGui(MUIElement, Object, IEclipseContext) line: 666
> PartRenderingEngine$1.run() line: 537
> SafeRunner.run(ISafeRunnable) line: 42
> PartRenderingEngine.createGui(MUIElement, Object, IEclipseContext) line: 521
> ElementReferenceRenderer.createWidget(MUIElement, Object) line: 70
> PartRenderingEngine.createWidget(MUIElement, Object) line: 976
> PartRenderingEngine.safeCreateGui(MUIElement, Object, IEclipseContext) line: 652
> PartRenderingEngine.safeCreateGui(MUIElement) line: 758
> PartRenderingEngine.access$0(PartRenderingEngine, MUIElement) line: 729
> PartRenderingEngine$2.run() line: 723
> SafeRunner.run(ISafeRunnable) line: 42
> PartRenderingEngine.createGui(MUIElement) line: 707
> SashRenderer(SWTPartRenderer).processContents(MElementContainer<MUIElement>) line: 72
> SashRenderer.processContents(MElementContainer<MUIElement>) line: 151
> PartRenderingEngine.safeCreateGui(MUIElement, Object, IEclipseContext) line: 666
> PartRenderingEngine.safeCreateGui(MUIElement) line: 758
> PartRenderingEngine.access$0(PartRenderingEngine, MUIElement) line: 729
> PartRenderingEngine$2.run() line: 723
> SafeRunner.run(ISafeRunnable) line: 42
> PartRenderingEngine.createGui(MUIElement) line: 707
> SashRenderer(SWTPartRenderer).processContents(MElementContainer<MUIElement>) line: 72
> SashRenderer.processContents(MElementContainer<MUIElement>) line: 151
> PartRenderingEngine.safeCreateGui(MUIElement, Object, IEclipseContext) line: 666
> PartRenderingEngine.safeCreateGui(MUIElement) line: 758
> PartRenderingEngine.access$0(PartRenderingEngine, MUIElement) line: 729
> PartRenderingEngine$2.run() line: 723
> SafeRunner.run(ISafeRunnable) line: 42
> PartRenderingEngine.createGui(MUIElement) line: 707
> SashRenderer(SWTPartRenderer).processContents(MElementContainer<MUIElement>) line: 72
> SashRenderer.processContents(MElementContainer<MUIElement>) line: 151
> PartRenderingEngine.safeCreateGui(MUIElement, Object, IEclipseContext) line: 666
> PartRenderingEngine.safeCreateGui(MUIElement) line: 758
> PartRenderingEngine.access$0(PartRenderingEngine, MUIElement) line: 729
> PartRenderingEngine$2.run() line: 723
> SafeRunner.run(ISafeRunnable) line: 42
> PartRenderingEngine.createGui(MUIElement) line: 707
> PerspectiveRenderer(SWTPartRenderer).processContents(MElementContainer<MUIElement>) line: 72
> PerspectiveRenderer.processContents(MElementContainer<MUIElement>) line: 49
> PartRenderingEngine.safeCreateGui(MUIElement, Object, IEclipseContext) line: 666
> PartRenderingEngine.safeCreateGui(MUIElement) line: 758
> PartRenderingEngine.access$0(PartRenderingEngine, MUIElement) line: 729
> PartRenderingEngine$2.run() line: 723
> SafeRunner.run(ISafeRunnable) line: 42
> PartRenderingEngine.createGui(MUIElement) line: 707
> PerspectiveStackRenderer.showTab(MUIElement) line: 82
> PerspectiveStackRenderer(LazyStackRenderer).postProcess(MUIElement) line: 103
> PerspectiveStackRenderer.postProcess(MUIElement) line: 63
> PartRenderingEngine.safeCreateGui(MUIElement, Object, IEclipseContext) line: 670
> PartRenderingEngine.safeCreateGui(MUIElement) line: 758
> PartRenderingEngine.access$0(PartRenderingEngine, MUIElement) line: 729
> PartRenderingEngine$2.run() line: 723
> SafeRunner.run(ISafeRunnable) line: 42
> PartRenderingEngine.createGui(MUIElement) line: 707
> SashRenderer(SWTPartRenderer).processContents(MElementContainer<MUIElement>) line: 72
> SashRenderer.processContents(MElementContainer<MUIElement>) line: 151
> PartRenderingEngine.safeCreateGui(MUIElement, Object, IEclipseContext) line: 666
> PartRenderingEngine.safeCreateGui(MUIElement) line: 758
> PartRenderingEngine.access$0(PartRenderingEngine, MUIElement) line: 729
> PartRenderingEngine$2.run() line: 723
> SafeRunner.run(ISafeRunnable) line: 42
> PartRenderingEngine.createGui(MUIElement) line: 707
> WBWRenderer(SWTPartRenderer).processContents(MElementContainer<MUIElement>) line: 72
> WBWRenderer.processContents(MElementContainer<MUIElement>) line: 614
> PartRenderingEngine.safeCreateGui(MUIElement, Object, IEclipseContext) line: 666
> PartRenderingEngine.safeCreateGui(MUIElement) line: 758
> PartRenderingEngine.access$0(PartRenderingEngine, MUIElement) line: 729
> PartRenderingEngine$2.run() line: 723
> SafeRunner.run(ISafeRunnable) line: 42
> PartRenderingEngine.createGui(MUIElement) line: 707
> PartRenderingEngine$4.run() line: 1066
> Realm.runWithDefault(Realm, Runnable) line: 336
> PartRenderingEngine.run(MApplicationElement, IEclipseContext) line: 1023
> E4Workbench.createAndRunUI(MApplicationElement) line: 157
> Workbench$5.run() line: 651
> Realm.runWithDefault(Realm, Runnable) line: 336
> Workbench.createAndRunWorkbench(Display, WorkbenchAdvisor) line: 595
> PlatformUI.createAndRunWorkbench(Display, WorkbenchAdvisor) line: 150
> IDEApplication.start(IApplicationContext) line: 138
> EclipseAppHandle.run(Object) line: 196
> EclipseAppLauncher.runApplication(Object) line: 134
> EclipseAppLauncher.start(Object) line: 104
> EclipseStarter.run(Object) line: 388
> EclipseStarter.run(String[], Runnable) line: 243
> NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native method]
> NativeMethodAccessorImpl.invoke(Object, Object[]) line: 62
> DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 43
> Method.invoke(Object, Object...) line: 498
> Main.invokeFramework(String[], URL[]) line: 670
> Main.basicRun(String[]) line: 609
> Main.run(String[]) line: 1516
> Main.main(String[]) line: 1489
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
&&(x86%7C%7Cx86_64))&&!beaker/427/artifact/eclipse/screenshots/testInstall(org.jboss.tools.tests.installation.InstallFromCentralTest).jpeg){kind=link}