[JBoss JIRA] (JBIDE-14727) SeamRuntimeDetectionTest test failure
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14727?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-14727:
--------------------------------------
Assignee: Snjezana Peco (was: Alexey Kazakov)
It has. See https://github.com/jbosstools/jbosstools-javaee/commit/ba719766f76064ad5c...
> SeamRuntimeDetectionTest test failure
> -------------------------------------
>
> Key: JBIDE-14727
> URL: https://issues.jboss.org/browse/JBIDE-14727
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Affects Versions: 4.1.0.Beta1
> Environment: RHEL 5 x86_64 Oracle JDK 1.7
> Reporter: Victor Rubezhny
> Assignee: Snjezana Peco
> Fix For: 4.1.0.Beta2
>
>
> Issue is reproducible not only on RHEL 6 x86, Oracle JDK 1.6 configuration as well.
> {code}org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionTest.testSeamFoundTwice (from org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionAllTests)
> Failing for the past 15 builds (Since #381 )
> Took 1.3 sec.
> add description
> Error Message
> expected:<1> but was:<2>
> Stacktrace
> java.lang.AssertionError: expected:<1> but was:<2>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:743)
> at org.junit.Assert.assertEquals(Assert.java:118)
> at org.junit.Assert.assertEquals(Assert.java:555)
> at org.junit.Assert.assertEquals(Assert.java:542)
> at org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionTest.testSeamFoundTwice(SeamRuntimeDetectionTest.java:368)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> {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
11 years, 1 month
[JBoss JIRA] (JBIDE-14641) Error when viewing source of page and VPE is set as default HTML editor
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14641?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-14641:
-----------------------------------------------
That was not enough. Palette will not work well, if there is no file available. Besides, Properties view also throws exceptions in that case. I sent new pull request in which palette will not appear and properties sheet will not send queries to kb model when file is not available.
> Error when viewing source of page and VPE is set as default HTML editor
> -----------------------------------------------------------------------
>
> Key: JBIDE-14641
> URL: https://issues.jboss.org/browse/JBIDE-14641
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim
> Affects Versions: 4.1.0.Beta1
> Environment: JBDS 7.0.0 Beta1-v20130519-0601-B206, Linux 64bit, Java Sun 1.6
> Reporter: Vlado Pakan
> Assignee: Viacheslav Kabanovich
> Priority: Critical
> Fix For: 4.1.0.Beta2
>
>
> 1. Open Window > Preferences > General > Editors > File Associations
> 2. Select *.HTML as File type
> 3. Select JBoss Tools HTML Editor and set it as default
> 4. Open page www.jboss.org in BrowserSim
> 5. Choose context menu View Page Source
> ERROR: Error dialog is displayed and this error appears in Error Log:
> Problems occurred when invoking code from plug-in: "org.eclipse.ui.workbench".
> {noformat}
> java.lang.NullPointerException
> at org.jboss.tools.jst.jsp.jspeditor.PalettePageImpl.attach(PalettePageImpl.java:64)
> at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditor.getAdapter(JSPMultiPageEditor.java:729)
> at org.eclipse.gef.ui.views.palette.PaletteView.doCreatePage(PaletteView.java:101)
> at org.eclipse.ui.part.PageBookView.createPage(PageBookView.java:411)
> at org.eclipse.ui.part.PageBookView.partActivated(PageBookView.java:754)
> at org.eclipse.ui.part.PageBookView$4.partActivated(PageBookView.java:1044)
> at org.eclipse.ui.internal.WorkbenchPage$12.run(WorkbenchPage.java:4541)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.WorkbenchPage.firePartActivated(WorkbenchPage.java:4539)
> at org.eclipse.ui.internal.WorkbenchPage.access$16(WorkbenchPage.java:4519)
> at org.eclipse.ui.internal.WorkbenchPage$E4PartListener.partActivated(WorkbenchPage.java:181)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl$2.run(PartServiceImpl.java:192)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.firePartActivated(PartServiceImpl.java:190)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:588)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:548)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:537)
> at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:3131)
> at org.eclipse.ui.internal.WorkbenchPage.access$22(WorkbenchPage.java:3048)
> at org.eclipse.ui.internal.WorkbenchPage$8.run(WorkbenchPage.java:3030)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3026)
> at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2990)
> at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2973)
> at org.jboss.tools.vpe.browsersim.eclipse.callbacks.ViewSourceCallback.openInMemoryHtmlEditor(ViewSourceCallback.java:90)
> at org.jboss.tools.vpe.browsersim.eclipse.callbacks.ViewSourceCallback.access$0(ViewSourceCallback.java:73)
> at org.jboss.tools.vpe.browsersim.eclipse.callbacks.ViewSourceCallback$1.run(ViewSourceCallback.java:68)
> 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:3692)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3341)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1108)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:992)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:137)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:600)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:555)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
> 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)
> {noformat}
--
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
11 years, 1 month
[JBoss JIRA] (JBIDE-14734) JQuery Mobile Palette Wizards appear on wrong display
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14734?page=com.atlassian.jira.plugi... ]
Daniel Azarov commented on JBIDE-14734:
---------------------------------------
It looks like on Windows (and probably on Mac too) the second display has negative x coordinate.
In this case we should remove "if(x < 0) x = 0;" from DropWizardDialog
> JQuery Mobile Palette Wizards appear on wrong display
> -----------------------------------------------------
>
> Key: JBIDE-14734
> URL: https://issues.jboss.org/browse/JBIDE-14734
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.1.0.Beta1
> Environment: Mac Os, Windows 8
> Reporter: Daniel Azarov
> Assignee: Daniel Azarov
> Fix For: 4.1.0.Beta2
>
>
> Reproduced on follow configuration:
> Two displays, main display on the right, second display on the left.
> Test case:
> EXECUTE:
> 1. Open JBDS
> 2. Open following html file in Visual Page Editor
> {code}
> <!DOCTYPE html>
> {code}
> 3. Place JBDS on the left display
> 4. Try do drop elements from jQuery Mobile Palette to the editor
> FAIL: Dialog appears on the right display
--
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
11 years, 1 month
[JBoss JIRA] (JBIDE-14734) JQuery Mobile Palette Wizards appear on wrong display
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14734?page=com.atlassian.jira.plugi... ]
Daniel Azarov updated JBIDE-14734:
----------------------------------
Issue Type: Bug (was: Feature Request)
> JQuery Mobile Palette Wizards appear on wrong display
> -----------------------------------------------------
>
> Key: JBIDE-14734
> URL: https://issues.jboss.org/browse/JBIDE-14734
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.1.0.Beta1
> Environment: Mac Os, Windows 8
> Reporter: Daniel Azarov
> Assignee: Daniel Azarov
> Fix For: 4.1.0.Beta2
>
>
> Reproduced on follow configuration:
> Two displays, main display on the right, second display on the left.
> Test case:
> EXECUTE:
> 1. Open JBDS
> 2. Open following html file in Visual Page Editor
> {code}
> <!DOCTYPE html>
> {code}
> 3. Place JBDS on the left display
> 4. Try do drop elements from jQuery Mobile Palette to the editor
> FAIL: Dialog appears on the right display
--
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
11 years, 1 month
[JBoss JIRA] (JBIDE-14734) JQuery Mobile Palette Wizards appear on wrong display
by Daniel Azarov (JIRA)
Daniel Azarov created JBIDE-14734:
-------------------------------------
Summary: JQuery Mobile Palette Wizards appear on wrong display
Key: JBIDE-14734
URL: https://issues.jboss.org/browse/JBIDE-14734
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: jsp/jsf/xml/html source editing
Affects Versions: 4.1.0.Beta1
Environment: Mac Os, Windows 8
Reporter: Daniel Azarov
Assignee: Daniel Azarov
Fix For: 4.1.0.Beta2
Reproduced on follow configuration:
Two displays, main display on the right, second display on the left.
Test case:
EXECUTE:
1. Open JBDS
2. Open following html file in Visual Page Editor
{code}
<!DOCTYPE html>
{code}
3. Place JBDS on the left display
4. Try do drop elements from jQuery Mobile Palette to the editor
FAIL: Dialog appears on the right display
--
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
11 years, 1 month
[JBoss JIRA] (JBIDE-14727) SeamRuntimeDetectionTest test failure
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14727?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-14727:
---------------------------------------
It seems that https://github.com/jbosstools/jbosstools-javaee/pull/82 hasn't been applied correctly.
> SeamRuntimeDetectionTest test failure
> -------------------------------------
>
> Key: JBIDE-14727
> URL: https://issues.jboss.org/browse/JBIDE-14727
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Affects Versions: 4.1.0.Beta1
> Environment: RHEL 5 x86_64 Oracle JDK 1.7
> Reporter: Victor Rubezhny
> Fix For: 4.1.0.Beta2
>
>
> Issue is reproducible not only on RHEL 6 x86, Oracle JDK 1.6 configuration as well.
> {code}org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionTest.testSeamFoundTwice (from org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionAllTests)
> Failing for the past 15 builds (Since #381 )
> Took 1.3 sec.
> add description
> Error Message
> expected:<1> but was:<2>
> Stacktrace
> java.lang.AssertionError: expected:<1> but was:<2>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:743)
> at org.junit.Assert.assertEquals(Assert.java:118)
> at org.junit.Assert.assertEquals(Assert.java:555)
> at org.junit.Assert.assertEquals(Assert.java:542)
> at org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionTest.testSeamFoundTwice(SeamRuntimeDetectionTest.java:368)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> {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
11 years, 1 month
[JBoss JIRA] (JBIDE-14727) SeamRuntimeDetectionTest test failure
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14727?page=com.atlassian.jira.plugi... ]
Snjezana Peco reassigned JBIDE-14727:
-------------------------------------
Assignee: Alexey Kazakov
> SeamRuntimeDetectionTest test failure
> -------------------------------------
>
> Key: JBIDE-14727
> URL: https://issues.jboss.org/browse/JBIDE-14727
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Affects Versions: 4.1.0.Beta1
> Environment: RHEL 5 x86_64 Oracle JDK 1.7
> Reporter: Victor Rubezhny
> Assignee: Alexey Kazakov
> Fix For: 4.1.0.Beta2
>
>
> Issue is reproducible not only on RHEL 6 x86, Oracle JDK 1.6 configuration as well.
> {code}org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionTest.testSeamFoundTwice (from org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionAllTests)
> Failing for the past 15 builds (Since #381 )
> Took 1.3 sec.
> add description
> Error Message
> expected:<1> but was:<2>
> Stacktrace
> java.lang.AssertionError: expected:<1> but was:<2>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:743)
> at org.junit.Assert.assertEquals(Assert.java:118)
> at org.junit.Assert.assertEquals(Assert.java:555)
> at org.junit.Assert.assertEquals(Assert.java:542)
> at org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionTest.testSeamFoundTwice(SeamRuntimeDetectionTest.java:368)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> {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
11 years, 1 month