[JBoss JIRA] (JBIDE-16382) JUnit Test failure: testELTooltip(org.jboss.tools.cdi.seam.core.test.international.SeamResourceBundleELTooltipTest)
by Victor Rubezhny (JIRA)
Victor Rubezhny created JBIDE-16382:
---------------------------------------
Summary: JUnit Test failure: testELTooltip(org.jboss.tools.cdi.seam.core.test.international.SeamResourceBundleELTooltipTest)
Key: JBIDE-16382
URL: https://issues.jboss.org/browse/JBIDE-16382
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: cdi
Affects Versions: 4.1.1.Final
Reporter: Victor Rubezhny
Assignee: Victor Rubezhny
Fix For: 4.1.2.Final
See <http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-javaee_mas...>:
{code}
Failed
org.jboss.tools.cdi.seam.core.test.international.SeamResourceBundleELTooltipTest.testELTooltip (from org.jboss.tools.cdi.seam.core.test.CDISeamCoreAllTests)
Failing for the past 15 builds (Since #521 )
Took 0.12 sec.
Error Message
Hover exists but its value is not expected: Hover Text: [/* Font definitions */ html { font-family: 'Sans',sans-serif; font-size: 10pt; font-style: normal; font-weight: normal; } body, h1, h2, h3, h4, h5, h6, p, table, td, caption, th, ul, ol, dl, li, dd, dt { font-size: 1em; } pre { font-family: monospace; } /* Margins */ body { overflow: auto; margin-top: 0px; margin-bottom: 0.5em; margin-left: 0.3em; margin-right: 0px; } h1 { margin-top: 0.3em; margin-bottom: 0.04em; } h2 { margin-top: 2em; margin-bottom: 0.25em; } h3 { margin-top: 1.7em; margin-bottom: 0.25em; } h4 { margin-top: 2em; margin-bottom: 0.3em; } h5 { margin-top: 0px; margin-bottom: 0px; } p { margin-top: 1em; margin-bottom: 1em; } pre { margin-left: 0.6em; } ul { margin-top: 0px; margin-bottom: 1em; margin-left: 1em; padding-left: 1em;} li { margin-top: 0px; margin-bottom: 0px; } li p { margin-top: 0px; margin-bottom: 0px; } ol { margin-top: 0px; margin-bottom: 1em; margin-left: 1em; padding-left: 1em; } dl { margin-top: 0px; margin-bottom: 1em; } dt { margin-top: 0px; margin-bottom: 0px; font-weight: bold; } dd { margin-top: 0px; margin-bottom: 0px; } /* Styles and colors */ a:link { color: #0000FF; } a:hover { color: #000080; } a:visited { text-decoration: underline; } a.header:link { text-decoration: none; color: #000000 } a.header:visited { text-decoration: none; color: #000000 } a.header:hover { text-decoration: underline; color: #000080; } h4 { font-style: italic; } strong { font-weight: bold; } em { font-style: italic; } var { font-style: italic; } th { font-weight: bold; } Base Name: messagesResource Bundle: /SeamCoreTest/src/messages.propertiesResource Bundle: /SeamCoreTest/src/messages_de.properties] Expected Value: [Base Name: messagesResource Bundle: /SeamCoreTest/src/messages.propertiesResource Bundle: /SeamCoreTest/src/messages_de.properties]
Stacktrace
junit.framework.AssertionFailedError: Hover exists but its value is not expected:
Hover Text: [/* Font definitions */ html { font-family: 'Sans',sans-serif; font-size: 10pt; font-style: normal; font-weight: normal; } body, h1, h2, h3, h4, h5, h6, p, table, td, caption, th, ul, ol, dl, li, dd, dt { font-size: 1em; } pre { font-family: monospace; } /* Margins */ body { overflow: auto; margin-top: 0px; margin-bottom: 0.5em; margin-left: 0.3em; margin-right: 0px; } h1 { margin-top: 0.3em; margin-bottom: 0.04em; } h2 { margin-top: 2em; margin-bottom: 0.25em; } h3 { margin-top: 1.7em; margin-bottom: 0.25em; } h4 { margin-top: 2em; margin-bottom: 0.3em; } h5 { margin-top: 0px; margin-bottom: 0px; } p { margin-top: 1em; margin-bottom: 1em; } pre { margin-left: 0.6em; } ul { margin-top: 0px; margin-bottom: 1em; margin-left: 1em; padding-left: 1em;} li { margin-top: 0px; margin-bottom: 0px; } li p { margin-top: 0px; margin-bottom: 0px; } ol { margin-top: 0px; margin-bottom: 1em; margin-left: 1em; padding-left: 1em; } dl { margin-top: 0px; margin-bottom: 1em; } dt { margin-top: 0px; margin-bottom: 0px; font-weight: bold; } dd { margin-top: 0px; margin-bottom: 0px; } /* Styles and colors */ a:link { color: #0000FF; } a:hover { color: #000080; } a:visited { text-decoration: underline; } a.header:link { text-decoration: none; color: #000000 } a.header:visited { text-decoration: none; color: #000000 } a.header:hover { text-decoration: underline; color: #000080; } h4 { font-style: italic; } strong { font-weight: bold; } em { font-style: italic; } var { font-style: italic; } th { font-weight: bold; } Base Name: messagesResource Bundle: /SeamCoreTest/src/messages.propertiesResource Bundle: /SeamCoreTest/src/messages_de.properties]
Expected Value: [Base Name: messagesResource Bundle: /SeamCoreTest/src/messages.propertiesResource Bundle: /SeamCoreTest/src/messages_de.properties]
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.Assert.assertTrue(Assert.java:22)
at junit.framework.TestCase.assertTrue(TestCase.java:192)
at org.jboss.tools.cdi.seam.core.test.international.SeamResourceBundleELTooltipTest.doELTooltipTest(SeamResourceBundleELTooltipTest.java:62)
at org.jboss.tools.cdi.seam.core.test.international.SeamResourceBundleELTooltipTest.testELTooltip(SeamResourceBundleELTooltipTest.java:104)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at junit.framework.TestCase.runTest(TestCase.java:176)
at junit.framework.TestCase.runBare(TestCase.java:141)
at junit.framework.TestResult$1.protect(TestResult.java:122)
at junit.framework.TestResult.runProtected(TestResult.java:142)
at junit.framework.TestResult.run(TestResult.java:125)
at junit.framework.TestCase.run(TestCase.java:129)
at junit.framework.TestSuite.runTest(TestSuite.java:255)
at junit.framework.TestSuite.run(TestSuite.java:250)
at junit.framework.TestSuite.runTest(TestSuite.java:255)
at junit.framework.TestSuite.run(TestSuite.java:250)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:23)
at junit.extensions.TestSetup$1.protect(TestSetup.java:23)
at junit.framework.TestResult.runProtected(TestResult.java:142)
at junit.extensions.TestSetup.run(TestSetup.java:27)
at junit.framework.TestSuite.runTest(TestSuite.java:255)
at junit.framework.TestSuite.run(TestSuite.java:250)
at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)
at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123)
at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164)
at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110)
at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:175)
at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:123)
at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:86)
at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication$1.run(AbstractUITestApplication.java:35)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3746)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3394)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1122)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1006)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:146)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:611)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:565)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:125)
at org.eclipse.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:31)
at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:114)
at org.eclipse.tycho.surefire.osgibooter.UITestApplication.start(UITestApplication.java:37)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:109)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:80)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:372)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:226)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (JBIDE-16332) VisualEditor: Use JavaFX WebView to render JSP/XHTML/HTML pages at design time
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16332?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-16332:
---------------------------------------
*SWT WebKit*
SWT Webkit integration
|| || Java7 32bit || Java7 64bit || Java8 32bit || Java8 64bit ||
|| Windows 32bit | | N/A | | N/A |
|| Windows 64bit | | *X* | | *X* |
|| OS X 32bit | N/A | N/A | N/A | N/A |
|| OS X 64bit | *X* | | *X* | |
|| Linux 32bit ** | | N/A | | N/A |
|| Linux 64bit ** | | | | |
\* Both GTK 2 and GTK 3 supported
Advantages:
* Support for GTK 2 and 3 under linux
* Uses OS installed webkit that comes with iTunes on Windows, Safari on Mac OS X (?), libwebkit-3 on Linux
* Native code is open source
Disadvantages:
* Implemented API allows basic browser operations and doesn't provides API to access DOM model
* No 64 bit support on Windows
Performance:
* Good performance
> VisualEditor: Use JavaFX WebView to render JSP/XHTML/HTML pages at design time
> ------------------------------------------------------------------------------
>
> Key: JBIDE-16332
> URL: https://issues.jboss.org/browse/JBIDE-16332
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: visual-page-editor-core
> Affects Versions: 4.2.x
> Reporter: Denis Golovin
> Assignee: Denis Golovin
>
> Questions to answer:
> 1) compatibility when both osgi hooks in place our and e(fx)clipse
> 2) is it working with gtk3
> 3) check how to add osgi hooks parameters into user's eclipse when installing from update site (p2 tochpoints should help)
> 4) how javafx load webkit and how it collides with eclipse loaded web kit
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (JBIDE-16381) Application wizard: wizard will create app and import, but wont create adapter and wont close
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16381?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-16381:
-------------------------------------
Steps to Reproduce:
# EXEC: launch application wizard and provide some name, type, etc
# EXEC: on the 2nd page check *Create and set up a server for easy publishing to OpenShift*
# EXEC: hit Finish
Result:
Application gets created, the project gets imported but the wizard wont close.
!stop-at-page2-and-wont-close.png!
Upcon "Cancel"-ing it you'll see that the server adapter is not created
was:
# EXEC: launch application wizard and provide some name, type, etc
# EXEC: on the 2nd page check *Create and set up a server for easy pshing to OpenShift*
# EXEC: hit Finish
Result:
Application gets created, the project gets imported but the wizard wont close.
!stop-at-page2-and-wont-close.png!
Upcon "Cancel"-ing it you'll see that the server adapter is not created
> Application wizard: wizard will create app and import, but wont create adapter and wont close
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-16381
> URL: https://issues.jboss.org/browse/JBIDE-16381
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Alpha1
> Reporter: Andre Dietisheim
> Priority: Critical
> Fix For: 4.2.0.Alpha1
>
> Attachments: stop-at-page2-and-wont-close.png
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (JBIDE-16290) Fixing SWT issues in Luna
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16290?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-16290:
----------------------------------
Description:
This ticket is meant to list the bugs related to GTK3 affecting JBDS:
* JBIDE-16280 VPE/XulRunner crashes workbench
* https://bugs.eclipse.org/bugs/show_bug.cgi?id=425692 (Import Existing Maven Project)
* https://bugs.eclipse.org/bugs/show_bug.cgi?id=420581
* Central tests uses SWT_GTK3=0 in its pom.
* https://bugs.eclipse.org/bugs/show_bug.cgi?id=421127
* https://bugs.eclipse.org/bugs/show_bug.cgi?id=425123
We should make sure all SWT issues we met are reported upstream and that we provide the necessary assistance to SWT developers to make sure everything will be stable for Luna/GA.
On Linux, most issues can be "hidden" by setting SWT_GTK3=0, but that's definitely not something we want to rely on for JBDS, as SWT over GTK2 will not be maintained in future.
was:
This ticket is meant to list the bugs related to GTK3 affecting JBDS:
* JBIDE-16280 VPE/XulRunner crashes workbench
* https://bugs.eclipse.org/bugs/show_bug.cgi?id=420581
* Central tests uses SWT_GTK3=0 in its pom.
* https://bugs.eclipse.org/bugs/show_bug.cgi?id=421127
* https://bugs.eclipse.org/bugs/show_bug.cgi?id=425123
We should make sure all SWT issues we met are reported upstream and that we provide the necessary assistance to SWT developers to make sure everything will be stable for Luna/GA.
On Linux, most issues can be "hidden" by setting SWT_GTK3=0, but that's definitely not something we want to rely on for JBDS, as SWT over GTK2 will not be maintained in future.
> Fixing SWT issues in Luna
> -------------------------
>
> Key: JBIDE-16290
> URL: https://issues.jboss.org/browse/JBIDE-16290
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform
> Reporter: Mickael Istria
> Assignee: Snjezana Peco
> Fix For: 4.2.0.Alpha2
>
> Attachments: Java - Eclipse _001.png, luna-crashing-on-outcomplete.ogv
>
>
> This ticket is meant to list the bugs related to GTK3 affecting JBDS:
> * JBIDE-16280 VPE/XulRunner crashes workbench
> * https://bugs.eclipse.org/bugs/show_bug.cgi?id=425692 (Import Existing Maven Project)
> * https://bugs.eclipse.org/bugs/show_bug.cgi?id=420581
> * Central tests uses SWT_GTK3=0 in its pom.
> * https://bugs.eclipse.org/bugs/show_bug.cgi?id=421127
> * https://bugs.eclipse.org/bugs/show_bug.cgi?id=425123
> We should make sure all SWT issues we met are reported upstream and that we provide the necessary assistance to SWT developers to make sure everything will be stable for Luna/GA.
> On Linux, most issues can be "hidden" by setting SWT_GTK3=0, but that's definitely not something we want to rely on for JBDS, as SWT over GTK2 will not be maintained in future.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (JBDS-1714) Allow creation of desktop icon only
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-1714?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-1714:
--------------------------------
Component/s: upstream
Marking it as upstream, because default IzPack panel is used.
> Allow creation of desktop icon only
> -----------------------------------
>
> Key: JBDS-1714
> URL: https://issues.jboss.org/browse/JBDS-1714
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: installer, upstream
> Reporter: Lukas Jungmann
> Priority: Minor
> Fix For: 5.x
>
>
> would be nice if installer would allow user to create dekstop icon without the need to create also menu icons. Currently user can let the installer create desktop icon only if creation of start-menu icons is selected
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months