[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-5395) Fix JsfAllTests.testCorrectDoctypeOnFileFromJarArchive

Maxim Areshkau (JIRA) jira-events at lists.jboss.org
Mon Dec 7 11:21:29 EST 2009


    [ https://jira.jboss.org/jira/browse/JBIDE-5395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12498637#action_12498637 ] 

Maxim Areshkau commented on JBIDE-5395:
---------------------------------------

This issue related to changes which has been made in JBIDE-4635. This test has been fixed in trunk(https://jira.jboss.org/jira/browse/JBIDE-5325).
Without it doctype detection works not correctly for files from jar. I don't think that I should commit changes of(JBIDE-5325) into branch. 

> Fix JsfAllTests.testCorrectDoctypeOnFileFromJarArchive
> ------------------------------------------------------
>
>                 Key: JBIDE-5395
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-5395
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JSF, Visual Page Editor core
>    Affects Versions: 3.1.0.M4
>            Reporter: Daniel Azarov
>            Assignee: Maxim Areshkau
>             Fix For: 3.1.0.CR1
>
>
> Last 3 builds report problem:
> java.lang.NullPointerException
> 	at org.jboss.tools.vpe.ui.test.TestUtil.getVpeVisualDocument(TestUtil.java:386)
> 	at org.jboss.tools.jsf.vpe.jsf.test.jbide.JBIDE4510Test.testCorrectDoctypeOnFileFromJarArchive(JBIDE4510Test.java:81)
> 	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
> 	at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
> 	at junit.extensions.TestSetup.run(TestSetup.java:25)
> 	at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:354)
> 	at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:206)
> 	at org.eclipse.test.UITestApplication$3.run(UITestApplication.java:195)
> 	at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> 	at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134)
> 	at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3468)
> 	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3115)
> 	at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405)
> 	at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369)
> 	at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221)
> 	at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500)
> 	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> 	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493)
> 	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> 	at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113)
> 	at org.eclipse.test.UITestApplication.runApplication(UITestApplication.java:138)
> 	at org.eclipse.test.UITestApplication.run(UITestApplication.java:60)
> 	at org.eclipse.test.UITestApplication.start(UITestApplication.java:210)
> 	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194)
> 	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:368)
> 	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
> 	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559)
> 	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
> 	at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
> 	at org.eclipse.equinox.launcher.Main.main(Main.java:1287)
> 	at org.eclipse.core.launcher.Main.main(Main.java:34)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the jbosstools-issues mailing list