[JBoss JIRA] (JBDS-4182) loader constraint violation in Cordova
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4182?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4182:
-----------------------------
Component/s: (was: rhscl)
(was: target-platform)
> loader constraint violation in Cordova
> --------------------------------------
>
> Key: JBDS-4182
> URL: https://issues.jboss.org/browse/JBDS-4182
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: aerogear-hybrid, build, rpm
> Affects Versions: 10.2.0.AM2
> Environment: Installed:
> {code}
> Installed Packages
> Name : rh-eclipse46-devstudio
> Arch : x86_64
> Epoch : 0
> Version : 10.2
> Release : 0.20161028.1959.el7
> Size : 371 M
> Repo : @System
> From repo : rh-eclipse46-devstudio-snapshot-10.2
> Summary : Red Hat Developer Studio
> URL : http://developers.redhat.com/products/devstudio/overview/
> License : EPL
> Description : Red Hat Developer Studio.
> {code}
> On Fedora 24 w/ JDK 8.
> Reporter: Nick Boldt
> Assignee: Gorkem Ercan
> Priority: Blocker
> Fix For: 10.2.0.GA
>
>
> Trying to run the *Hybrid Mobile Project* quickstart:
> {code}
> Unhandled event loop exception
> org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NoClassDefFoundError: org/apache/http/client/cache/HttpCacheStorage)
> at org.eclipse.swt.SWT.error(SWT.java:4533)
> at org.eclipse.swt.SWT.error(SWT.java:4448)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:185)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4528)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4146)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1121)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1022)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:687)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:604)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
> 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:497)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1519)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1492)
> Caused by: java.lang.NoClassDefFoundError: org/apache/http/client/cache/HttpCacheStorage
> at org.eclipse.thym.ui.plugins.internal.CordovaPluginSelectionPage.<init>(CordovaPluginSelectionPage.java:99)
> at org.eclipse.thym.ui.plugins.internal.CordovaPluginSelectionPage.<init>(CordovaPluginSelectionPage.java:129)
> at org.eclipse.thym.ui.wizard.project.NewHybridProjectWizard.addPages(NewHybridProjectWizard.java:183)
> at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:585)
> at org.eclipse.jface.window.Window.create(Window.java:426)
> at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1095)
> at org.eclipse.jface.window.Window.open(Window.java:783)
> at org.jboss.tools.central.internal.WizardSupport.openWizard(WizardSupport.java:71)
> at org.jboss.tools.central.editors.GettingStartedHtmlPage$9.run(GettingStartedHtmlPage.java:431)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:182)
> ... 24 more
> Caused by: java.lang.ClassNotFoundException: org.apache.http.client.cache.HttpCacheStorage cannot be found by org.eclipse.thym.core_2.0.0.201607041526
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:461)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:372)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:364)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 35 more
> eclipse.buildId=4.6.1.v20160920-1429
> java.version=1.8.0_65
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_CA
> Command-line arguments: -os linux -ws gtk -arch x86_64 -consolelog -console -debug -data /tmp/wksp-20161101-1105
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23491) Integration tests: CleanUpOS3 fails if no connection exists
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23491?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-23491:
------------------------------------------
merged into jbosstools-integration-tests/master
> Integration tests: CleanUpOS3 fails if no connection exists
> -----------------------------------------------------------
>
> Key: JBIDE-23491
> URL: https://issues.jboss.org/browse/JBIDE-23491
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.2.AM3
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: integration_tests, openshift_v3
> Fix For: 4.4.2.Final
>
>
> If you run [CleanUpOS3|https://github.com/jbosstools/jbosstools-integration-tests/blo...] without a connection it will fail producing a test error, which it shouldnt since it's just about cleaning up after tests.
> The reason for it is that the wait for the connection item in the OpenShift explorer tree is producing a CoreLayerException, while the class is catching a JFaceLayerException:
> {code:title=https://github.com/jbosstools/jbosstools-integration-tests/blob/master/plugins/org.jboss.tools.openshift.reddeer/src/org/jboss/tools/openshift/reddeer/utils/CleanUpOS3.java#L43}
> try {
> connection = explorer.getOpenShift3Connection();
> } catch (JFaceLayerException ex) {
> // There is no connection with such username, nothing happens
> }
> {code}
> The stack trace that is produced:
> {code}
> org.jboss.reddeer.core.exception.CoreLayerException: No matching widget found with Matcher matching when all matchers match: [Matcher matching widget with the same type as or type extending class org.eclipse.swt.widgets.Tree]
> class org.eclipse.e4.ui.workbench.renderers.swt.ContributedPartRenderer$2
> class org.eclipse.swt.widgets.Composite
> class org.eclipse.ui.part.PageBook
> class org.eclipse.swt.widgets.Tree
> class org.eclipse.ui.forms.widgets.Form with text ''
> class org.eclipse.ui.internal.forms.widgets.FormHeading with text ''
> class org.eclipse.ui.internal.forms.widgets.TitleRegion with text ''
> class org.eclipse.swt.widgets.Label with text ''
> class org.eclipse.ui.forms.widgets.LayoutComposite
> class org.eclipse.swt.widgets.Link with text 'No connections are available. Create a new connection with the <a>New Connection Wizard...</a>'
> at org.jboss.reddeer.core.lookup.WidgetLookup.activeWidget(WidgetLookup.java:108)
> at org.jboss.reddeer.core.lookup.WidgetLookup.activeWidget(WidgetLookup.java:78)
> at org.jboss.reddeer.swt.widgets.AbstractWidget.<init>(AbstractWidget.java:41)
> at org.jboss.reddeer.swt.impl.tree.AbstractTree.<init>(AbstractTree.java:35)
> at org.jboss.reddeer.swt.impl.tree.DefaultTree.<init>(DefaultTree.java:77)
> at org.jboss.reddeer.swt.impl.tree.DefaultTree.<init>(DefaultTree.java:37)
> at org.jboss.reddeer.swt.impl.tree.DefaultTree.<init>(DefaultTree.java:28)
> at org.jboss.tools.openshift.reddeer.view.OpenShiftExplorerView.getConnectionItem(OpenShiftExplorerView.java:276)
> at org.jboss.tools.openshift.reddeer.view.OpenShiftExplorerView.getOpenShift3Connection(OpenShiftExplorerView.java:267)
> at org.jboss.tools.openshift.reddeer.view.OpenShiftExplorerView.getOpenShift3Connection(OpenShiftExplorerView.java:253)
> at org.jboss.tools.openshift.reddeer.utils.CleanUpOS3.cleanUp(CleanUpOS3.java:43)
> 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.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at org.jboss.reddeer.junit.internal.runner.statement.RunAfters.evaluate(RunAfters.java:76)
> at org.jboss.reddeer.junit.internal.runner.statement.RunIAfterTestExtensions.evaluate(RunIAfterTestExtensions.java:61)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at org.jboss.reddeer.junit.internal.runner.RequirementsRunner.runChild(RequirementsRunner.java:175)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.jboss.reddeer.junit.internal.runner.statement.RunBefores.evaluate(RunBefores.java:79)
> at org.jboss.reddeer.junit.internal.runner.statement.FulfillRequirementsStatement.evaluate(FulfillRequirementsStatement.java:45)
> at org.jboss.reddeer.junit.internal.runner.statement.RunIBeforeClassExtensions.evaluate(RunIBeforeClassExtensions.java:72)
> at org.jboss.reddeer.junit.internal.runner.statement.RunAfters.evaluate(RunAfters.java:68)
> at org.jboss.reddeer.junit.internal.runner.statement.CleanUpRequirementStatement.evaluate(CleanUpRequirementStatement.java:44)
> at org.jboss.reddeer.junit.internal.runner.statement.RunIAfterClassExtensions.evaluate(RunIAfterClassExtensions.java:59)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.jboss.reddeer.junit.internal.runner.RequirementsRunner.run(RequirementsRunner.java:156)
> at org.junit.runners.Suite.runChild(Suite.java:128)
> at org.junit.runners.Suite.runChild(Suite.java:27)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.junit.runners.Suite.runChild(Suite.java:128)
> at org.junit.runners.Suite.runChild(Suite.java:27)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86)
> at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:678)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382)
> at org.jboss.reddeer.eclipse.core.RemotePluginTestRunner.main(RemotePluginTestRunner.java:68)
> at org.jboss.reddeer.eclipse.core.UITestApplication.runTests(UITestApplication.java:125)
> at org.eclipse.e4.ui.internal.workbench.swt.E4Testable$1.run(E4Testable.java:73)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.jboss.reddeer.common.exception.WaitTimeoutExpiredException: Timeout after: 1 s.: widget is found
> at org.jboss.reddeer.common.wait.AbstractWait.timeoutExceeded(AbstractWait.java:183)
> at org.jboss.reddeer.common.wait.AbstractWait.wait(AbstractWait.java:136)
> at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:101)
> at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:71)
> at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:56)
> at org.jboss.reddeer.common.wait.WaitUntil.<init>(WaitUntil.java:47)
> at org.jboss.reddeer.core.lookup.WidgetLookup.activeWidget(WidgetLookup.java:103)
> ... 60 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23491) Integration tests: CleanUpOS3 fails if no connection exists
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23491?page=com.atlassian.jira.plugi... ]
Andre Dietisheim closed JBIDE-23491.
------------------------------------
QE verified the PR. Closing.
> Integration tests: CleanUpOS3 fails if no connection exists
> -----------------------------------------------------------
>
> Key: JBIDE-23491
> URL: https://issues.jboss.org/browse/JBIDE-23491
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.2.AM3
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: integration_tests, openshift_v3
> Fix For: 4.4.2.Final
>
>
> If you run [CleanUpOS3|https://github.com/jbosstools/jbosstools-integration-tests/blo...] without a connection it will fail producing a test error, which it shouldnt since it's just about cleaning up after tests.
> The reason for it is that the wait for the connection item in the OpenShift explorer tree is producing a CoreLayerException, while the class is catching a JFaceLayerException:
> {code:title=https://github.com/jbosstools/jbosstools-integration-tests/blob/master/plugins/org.jboss.tools.openshift.reddeer/src/org/jboss/tools/openshift/reddeer/utils/CleanUpOS3.java#L43}
> try {
> connection = explorer.getOpenShift3Connection();
> } catch (JFaceLayerException ex) {
> // There is no connection with such username, nothing happens
> }
> {code}
> The stack trace that is produced:
> {code}
> org.jboss.reddeer.core.exception.CoreLayerException: No matching widget found with Matcher matching when all matchers match: [Matcher matching widget with the same type as or type extending class org.eclipse.swt.widgets.Tree]
> class org.eclipse.e4.ui.workbench.renderers.swt.ContributedPartRenderer$2
> class org.eclipse.swt.widgets.Composite
> class org.eclipse.ui.part.PageBook
> class org.eclipse.swt.widgets.Tree
> class org.eclipse.ui.forms.widgets.Form with text ''
> class org.eclipse.ui.internal.forms.widgets.FormHeading with text ''
> class org.eclipse.ui.internal.forms.widgets.TitleRegion with text ''
> class org.eclipse.swt.widgets.Label with text ''
> class org.eclipse.ui.forms.widgets.LayoutComposite
> class org.eclipse.swt.widgets.Link with text 'No connections are available. Create a new connection with the <a>New Connection Wizard...</a>'
> at org.jboss.reddeer.core.lookup.WidgetLookup.activeWidget(WidgetLookup.java:108)
> at org.jboss.reddeer.core.lookup.WidgetLookup.activeWidget(WidgetLookup.java:78)
> at org.jboss.reddeer.swt.widgets.AbstractWidget.<init>(AbstractWidget.java:41)
> at org.jboss.reddeer.swt.impl.tree.AbstractTree.<init>(AbstractTree.java:35)
> at org.jboss.reddeer.swt.impl.tree.DefaultTree.<init>(DefaultTree.java:77)
> at org.jboss.reddeer.swt.impl.tree.DefaultTree.<init>(DefaultTree.java:37)
> at org.jboss.reddeer.swt.impl.tree.DefaultTree.<init>(DefaultTree.java:28)
> at org.jboss.tools.openshift.reddeer.view.OpenShiftExplorerView.getConnectionItem(OpenShiftExplorerView.java:276)
> at org.jboss.tools.openshift.reddeer.view.OpenShiftExplorerView.getOpenShift3Connection(OpenShiftExplorerView.java:267)
> at org.jboss.tools.openshift.reddeer.view.OpenShiftExplorerView.getOpenShift3Connection(OpenShiftExplorerView.java:253)
> at org.jboss.tools.openshift.reddeer.utils.CleanUpOS3.cleanUp(CleanUpOS3.java:43)
> 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.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at org.jboss.reddeer.junit.internal.runner.statement.RunAfters.evaluate(RunAfters.java:76)
> at org.jboss.reddeer.junit.internal.runner.statement.RunIAfterTestExtensions.evaluate(RunIAfterTestExtensions.java:61)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at org.jboss.reddeer.junit.internal.runner.RequirementsRunner.runChild(RequirementsRunner.java:175)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.jboss.reddeer.junit.internal.runner.statement.RunBefores.evaluate(RunBefores.java:79)
> at org.jboss.reddeer.junit.internal.runner.statement.FulfillRequirementsStatement.evaluate(FulfillRequirementsStatement.java:45)
> at org.jboss.reddeer.junit.internal.runner.statement.RunIBeforeClassExtensions.evaluate(RunIBeforeClassExtensions.java:72)
> at org.jboss.reddeer.junit.internal.runner.statement.RunAfters.evaluate(RunAfters.java:68)
> at org.jboss.reddeer.junit.internal.runner.statement.CleanUpRequirementStatement.evaluate(CleanUpRequirementStatement.java:44)
> at org.jboss.reddeer.junit.internal.runner.statement.RunIAfterClassExtensions.evaluate(RunIAfterClassExtensions.java:59)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.jboss.reddeer.junit.internal.runner.RequirementsRunner.run(RequirementsRunner.java:156)
> at org.junit.runners.Suite.runChild(Suite.java:128)
> at org.junit.runners.Suite.runChild(Suite.java:27)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.junit.runners.Suite.runChild(Suite.java:128)
> at org.junit.runners.Suite.runChild(Suite.java:27)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86)
> at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:678)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382)
> at org.jboss.reddeer.eclipse.core.RemotePluginTestRunner.main(RemotePluginTestRunner.java:68)
> at org.jboss.reddeer.eclipse.core.UITestApplication.runTests(UITestApplication.java:125)
> at org.eclipse.e4.ui.internal.workbench.swt.E4Testable$1.run(E4Testable.java:73)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.jboss.reddeer.common.exception.WaitTimeoutExpiredException: Timeout after: 1 s.: widget is found
> at org.jboss.reddeer.common.wait.AbstractWait.timeoutExceeded(AbstractWait.java:183)
> at org.jboss.reddeer.common.wait.AbstractWait.wait(AbstractWait.java:136)
> at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:101)
> at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:71)
> at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:56)
> at org.jboss.reddeer.common.wait.WaitUntil.<init>(WaitUntil.java:47)
> at org.jboss.reddeer.core.lookup.WidgetLookup.activeWidget(WidgetLookup.java:103)
> ... 60 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBTIS-987) Update the descrition for SOA category in RH Central
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-987?page=com.atlassian.jira.plugin.... ]
Paul Leacu reassigned JBTIS-987:
--------------------------------
Assignee: Paul Leacu
> Update the descrition for SOA category in RH Central
> ----------------------------------------------------
>
> Key: JBTIS-987
> URL: https://issues.jboss.org/browse/JBTIS-987
> Project: JBoss Tools Integration Stack
> Issue Type: Task
> Components: distribution
> Affects Versions: 10.0.0.GA
> Reporter: Andrej Podhradsky
> Assignee: Paul Leacu
> Attachments: devstudio-is-10.0.0.GA-central.png
>
>
> At the moment the description for JBoss Integration and SOA Development says
> "Tools related to the development of Integration and SOA applications - includes support for BPEL, BPMN2, Drools, jBPM6 and KIE."
> But the category also contains Fuse and SwitchYard tools.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4150) use constraint violations in Thym/Aerogear
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4150?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4150:
-----------------------------
Summary: use constraint violations in Thym/Aerogear (was: org.eclipse.thym.ui :: Could not load Hybrid Mobile quickstart: NoClassDefFound: org/apache/http/client/cache/HttpCacheStorage)
> use constraint violations in Thym/Aerogear
> ------------------------------------------
>
> Key: JBDS-4150
> URL: https://issues.jboss.org/browse/JBDS-4150
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: aerogear-hybrid, build, rhscl, rpm, target-platform
> Affects Versions: 10.2.0.AM2
> Environment: Installed:
> {code}
> Installed Packages
> Name : rh-eclipse46-devstudio
> Arch : x86_64
> Epoch : 0
> Version : 10.2
> Release : 0.20161028.1959.el7
> Size : 371 M
> Repo : @System
> From repo : rh-eclipse46-devstudio-snapshot-10.2
> Summary : Red Hat Developer Studio
> URL : http://developers.redhat.com/products/devstudio/overview/
> License : EPL
> Description : Red Hat Developer Studio.
> {code}
> On Fedora 24 w/ JDK 8.
> Reporter: Nick Boldt
> Assignee: Gorkem Ercan
> Priority: Blocker
> Fix For: 10.2.0.GA
>
> Attachments: hybrid-mobile-quickstart-constraint-violation-ignored-seems-to-work.png, hybrid-mobile-quickstart-constraint-violation.png, jbds4150_irc_log.txt, o.a.httpcomponents.httpclient_rh-eclipse__vs__devstudio_tp.png, thym.test.failures.txt
>
>
> Trying to run the *Hybrid Mobile Project* quickstart:
> {code}
> Unhandled event loop exception
> org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NoClassDefFoundError: org/apache/http/client/cache/HttpCacheStorage)
> at org.eclipse.swt.SWT.error(SWT.java:4533)
> at org.eclipse.swt.SWT.error(SWT.java:4448)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:185)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4528)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4146)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1121)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1022)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:687)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:604)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
> 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:497)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1519)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1492)
> Caused by: java.lang.NoClassDefFoundError: org/apache/http/client/cache/HttpCacheStorage
> at org.eclipse.thym.ui.plugins.internal.CordovaPluginSelectionPage.<init>(CordovaPluginSelectionPage.java:99)
> at org.eclipse.thym.ui.plugins.internal.CordovaPluginSelectionPage.<init>(CordovaPluginSelectionPage.java:129)
> at org.eclipse.thym.ui.wizard.project.NewHybridProjectWizard.addPages(NewHybridProjectWizard.java:183)
> at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:585)
> at org.eclipse.jface.window.Window.create(Window.java:426)
> at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1095)
> at org.eclipse.jface.window.Window.open(Window.java:783)
> at org.jboss.tools.central.internal.WizardSupport.openWizard(WizardSupport.java:71)
> at org.jboss.tools.central.editors.GettingStartedHtmlPage$9.run(GettingStartedHtmlPage.java:431)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:182)
> ... 24 more
> Caused by: java.lang.ClassNotFoundException: org.apache.http.client.cache.HttpCacheStorage cannot be found by org.eclipse.thym.core_2.0.0.201607041526
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:461)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:372)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:364)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 35 more
> eclipse.buildId=4.6.1.v20160920-1429
> java.version=1.8.0_65
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_CA
> Command-line arguments: -os linux -ws gtk -arch x86_64 -consolelog -console -debug -data /tmp/wksp-20161101-1105
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBTIS-947) Installer with runtime doesn't automatically set the appropriated server
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-947?page=com.atlassian.jira.plugin.... ]
Paul Leacu closed JBTIS-947.
----------------------------
Resolution: Rejected
As discussed - we want the dialog tp appear top allow the user to choose to start the server.
> Installer with runtime doesn't automatically set the appropriated server
> ------------------------------------------------------------------------
>
> Key: JBTIS-947
> URL: https://issues.jboss.org/browse/JBTIS-947
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution
> Affects Versions: 10.0.0.CR1
> Environment: devstudio-integration-stack-rt-10.0.0.CR1-standalone-installer.jar
> Reporter: Andrej Podhradsky
> Assignee: Paul Leacu
> Priority: Minor
> Attachments: search_for_runtimes.png
>
>
> Installer with runtime doesn't automatically set the appropriated server. Instead of that there is a dialog 'Search for runtimes' when you start the IDE for the first time.
> !search_for_runtimes.png|thumbnail!
> Note that this is a different behavior as it is in Devstudio installer with EAP
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4133) org.jboss.tools.ws.jaxrs.core :: error occurred during JAX-RS Metamodel build - java.lang.NoClassDefFoundError: org/apache/lucene/analysis/standard/StandardAnalyzer
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4133?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-4133:
----------------------------------
JAX-RS error no longer occurs with this version of rpm installed:
{code}
$ dnf info rh-eclipse46-devstudio | grep -i Installed -A5
Installed Packages
Name : rh-eclipse46-devstudio
Arch : x86_64
Epoch : 0
Version : 10.2
Release : 0.20161116.1342.el7
{code}
> org.jboss.tools.ws.jaxrs.core :: error occurred during JAX-RS Metamodel build - java.lang.NoClassDefFoundError: org/apache/lucene/analysis/standard/StandardAnalyzer
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-4133
> URL: https://issues.jboss.org/browse/JBDS-4133
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, rpm, target-platform, webservices
> Affects Versions: 10.2.0.AM2
> Reporter: Nick Boldt
> Assignee: Xavier Coulon
> Priority: Blocker
> Fix For: 10.2.0.GA
>
> Attachments: image-2016-11-08-19-07-53-492.png, lucene3.5corevs.5.4.1analyzers-common.png, lucene3.5corevs.5.4.1queryparser.png, org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite.txt, org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite.txt, org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite.txt, osgi-console-lucene.png, TEST-org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite.xml, TEST-org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite.xml, TEST-org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite.xml
>
>
> I'm getting this problem after running the HTML5 quickstart. I've installed this [1] version of the rpm.
> {code}
> !ENTRY org.eclipse.core.jobs 4 2 2016-10-26 16:22:07.578
> !MESSAGE An internal error occurred during: "JAX-RS Metamodel build...".
> !STACK 0
> java.lang.NoClassDefFoundError: org/apache/lucene/analysis/standard/StandardAnalyzer
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.<init>(JaxrsMetamodel.java:163)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.create(JaxrsMetamodel.java:278)
> at org.jboss.tools.ws.jaxrs.core.metamodel.domain.JaxrsMetamodelLocator.get(JaxrsMetamodelLocator.java:120)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.ResourceChangedBuildJob.run(ResourceChangedBuildJob.java:68)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: java.lang.ClassNotFoundException: org.apache.lucene.analysis.standard.StandardAnalyzer cannot be found by org.jboss.tools.ws.jaxrs.core_1.9.2.v20161011-1002
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:461)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:372)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:364)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 5 more
> {code}
> [1] https://devstudio.jboss.com/10.0/snapshots/builds/devstudio.rpm_master/20...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4085) slow initial start up of rh-eclipse46-devstudio - disable usage constraint checking?
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4085?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-4085:
----------------------------------
https://bugzilla.redhat.com/show_bug.cgi?id=1392095 is now verified so... closing this too.
> slow initial start up of rh-eclipse46-devstudio - disable usage constraint checking?
> ------------------------------------------------------------------------------------
>
> Key: JBDS-4085
> URL: https://issues.jboss.org/browse/JBDS-4085
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: rhscl, rpm
> Reporter: Václav Kadlčík
> Assignee: Nick Boldt
> Fix For: 10.2.0.GA
>
> Attachments: disable-uses-by-default.patch, restart-after-installing-m2e-wtp-jsf-stuff-from-Central.txt, restart-after-installing-m2e-wtp-jsf-stuff-from-Central_full.txt, rh-eclipse46-devstudio10.2.log.20161028-1611.txt, unresolved-max.out, unresolved-mid.out, unresolved-min.out, workspace-max.log, workspace-mid.log, workspace-min.log
>
>
> Tested:
> * rh-eclipse46-devstudio-10.2-0.20161004.2205.el7.x86_64.rpm
> * rh-eclipse46 Beta (http://download-node-02.eng.bos.redhat.com/rel-eng/RHSCL-2.3-RHEL-7-Beta-...)
> rh-eclipse46 has its own unresolved bundles (https://bugzilla.redhat.com/show_bug.cgi?id=1381820). But when you add rh-eclipse46-devstudio, the number of unresolved symbols increases quite dramatically and initial start up times also get worse. (I guess that the two problems can be connected so I file them together but feel free to split them if I'm mistaken).
> I'm attaching "ss -s INSTALLED" and workspace logs for several scenarios:
> * "min" in the name means minimal install rh-eclipse46-devstudio
> * "mid" is for "yum install rh-eclipse46 rh-eclipse46-devstudio"
> * "max" is for "yum install 'rh-eclipse46*'" - all the available RPMs, including devstudio
> As for start up times, it looks like devstudio adds ~80s for one particular machine (Xeon with 16 cores 2.40GHz, 16 GB RAM). For example:
> initial start of rh-eclipse46: 40s
> same as above with rh-eclipse46-devstudio: 120s
> initial start of rh-eclipse46* except devstudio: 50s
> same as above with rh-eclipse46-devstudio: 140s
> Roland Grunberg managed to improve initial start up times in rh-eclise46 a few weeks ago (https://bugzilla.redhat.com/show_bug.cgi?id=1362178#c17). I don't know it it helps here but I'm linking it anyway...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4085) slow initial start up of rh-eclipse46-devstudio - disable usage constraint checking?
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4085?page=com.atlassian.jira.plugin.... ]
Nick Boldt closed JBDS-4085.
----------------------------
> slow initial start up of rh-eclipse46-devstudio - disable usage constraint checking?
> ------------------------------------------------------------------------------------
>
> Key: JBDS-4085
> URL: https://issues.jboss.org/browse/JBDS-4085
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: rhscl, rpm
> Reporter: Václav Kadlčík
> Assignee: Nick Boldt
> Fix For: 10.2.0.GA
>
> Attachments: disable-uses-by-default.patch, restart-after-installing-m2e-wtp-jsf-stuff-from-Central.txt, restart-after-installing-m2e-wtp-jsf-stuff-from-Central_full.txt, rh-eclipse46-devstudio10.2.log.20161028-1611.txt, unresolved-max.out, unresolved-mid.out, unresolved-min.out, workspace-max.log, workspace-mid.log, workspace-min.log
>
>
> Tested:
> * rh-eclipse46-devstudio-10.2-0.20161004.2205.el7.x86_64.rpm
> * rh-eclipse46 Beta (http://download-node-02.eng.bos.redhat.com/rel-eng/RHSCL-2.3-RHEL-7-Beta-...)
> rh-eclipse46 has its own unresolved bundles (https://bugzilla.redhat.com/show_bug.cgi?id=1381820). But when you add rh-eclipse46-devstudio, the number of unresolved symbols increases quite dramatically and initial start up times also get worse. (I guess that the two problems can be connected so I file them together but feel free to split them if I'm mistaken).
> I'm attaching "ss -s INSTALLED" and workspace logs for several scenarios:
> * "min" in the name means minimal install rh-eclipse46-devstudio
> * "mid" is for "yum install rh-eclipse46 rh-eclipse46-devstudio"
> * "max" is for "yum install 'rh-eclipse46*'" - all the available RPMs, including devstudio
> As for start up times, it looks like devstudio adds ~80s for one particular machine (Xeon with 16 cores 2.40GHz, 16 GB RAM). For example:
> initial start of rh-eclipse46: 40s
> same as above with rh-eclipse46-devstudio: 120s
> initial start of rh-eclipse46* except devstudio: 50s
> same as above with rh-eclipse46-devstudio: 140s
> Roland Grunberg managed to improve initial start up times in rh-eclise46 a few weeks ago (https://bugzilla.redhat.com/show_bug.cgi?id=1362178#c17). I don't know it it helps here but I'm linking it anyway...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-18912) Custom deploy dir with remote server using filesystem operations does not work
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18912?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-18912:
---------------------------------------
[~rob.stryker], my steps clearly included checking "Expose management port":
{quote}
2. Open server editor and check "Expose management port", check "Add scanners" and "Remove scanners", make sure the password is OK
{quote}
Also, when I tried this now, at first I had my admin password incorrect which resulted in an error in the Error log view.
But once I fixed that, I followed the steps again and I can still reproduce the issue:
First attempt to deploy into custom directory works, the project is found and deployed.
Second attempt fails, the project is found, but not deployed:
{code}
14:50:16,568 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) JBAS015012: Started FileSystemDeploymentService for directory /home/rasp/jbossqa/runtimes/jboss-eap-6.4.0/customdir
14:50:41,596 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found dynproj.war in deployment directory. To trigger deployment create a file called dynproj.war.dodeploy
{code}
To repeat, these are my steps to reproduce:
1. Create a remote server (remote, fs operations, no runtime) - eap 6.3
2. Open server editor and check "Expose management port", check "Add scanners" and "Remove scanners", make sure the password is OK
3. Go to Deployment tab in the editor, set up a custom dir on the remote host for deployment, save the editor
4. Create a simple dynamic web project
5. Start the server, in the server log you will see that the custom deployment scanner was added
6. Deploy your project (right-click server -> Add/Remove modules)
7. Check the server console - the project was deployed
8. Undeploy the project
9. Stop the server
10. Repeat 5. and 6., this time it will copy the project, but not create the .dodeploy marker, so the project will not deploy.
11. If you remove the project and deploy again now, it will work. But if you go all over again (i.e. new server start) it will not work
> Custom deploy dir with remote server using filesystem operations does not work
> ------------------------------------------------------------------------------
>
> Key: JBIDE-18912
> URL: https://issues.jboss.org/browse/JBIDE-18912
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.1.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Labels: help_wanted
> Fix For: 4.4.2.Final
>
>
> This is a follow up of JBIDE-17180 and JBIDE-13445 which added the option to add a custom deployment directory if your remote server is using filesystem operations (for management api it's not relevant since the deployment happens directly, no directory is used).
> Unfortunately it does not work. It seems I haven't really tried it when reviewing those other JIRAs because there were other obstacles.
> I tried this several times and still could not get it to work.
> Perhaps it might be worth to try and get this in the final 4.2.1.Final build?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months