[JBoss JIRA] Created: (JBIDE-5862) org.jboss.tools.jsf.vpe.jsf.test.jbide.EditingSPecialSymbolsVPE_JBIDE3810.compareVisualAndSourceTargets fails with: expected:<[ a] > but was:<[ >] >
by Nick Boldt (JIRA)
org.jboss.tools.jsf.vpe.jsf.test.jbide.EditingSPecialSymbolsVPE_JBIDE3810.compareVisualAndSourceTargets fails with: expected:<[ a] > but was:<[ >] >
-----------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-5862
URL: https://jira.jboss.org/jira/browse/JBIDE-5862
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JSF
Affects Versions: 3.1.0.CR2
Reporter: Nick Boldt
Assignee: Max Rydahl Andersen
Regression
JsfAllTests.testEditingSPecialSymbolsVPE_JBIDE3810
Failing for the past 1 build (Since #251 )
Took 13 sec.
add description
Error Message
expected:<[ a] > but was:<[ >] >
Stacktrace
junit.framework.ComparisonFailure: expected:<[
a]
> but was:<[ >]
>
at org.jboss.tools.jsf.vpe.jsf.test.jbide.EditingSPecialSymbolsVPE_JBIDE3810.compareVisualAndSourceTargets(EditingSPecialSymbolsVPE_JBIDE3810.java:160)
at org.jboss.tools.jsf.vpe.jsf.test.jbide.EditingSPecialSymbolsVPE_JBIDE3810.testEditingSPecialSymbolsVPE_JBIDE3810(EditingSPecialSymbolsVPE_JBIDE3810.java:58)
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)
http://hudson.qa.jboss.com/hudson/view/DevStudio/job/jbosstools-nightly-3...
--
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
14 years, 10 months
[JBoss JIRA] Created: (JBIDE-8869) 5 tests in JSF component failed with the same error in tearDown() method
by Victor Rubezhny (JIRA)
5 tests in JSF component failed with the same error in tearDown() method
------------------------------------------------------------------------
Key: JBIDE-8869
URL: https://issues.jboss.org/browse/JBIDE-8869
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jsp/jsf/xml source editing, testing
Affects Versions: 3.3.0.M1
Reporter: Victor Rubezhny
Assignee: Victor Rubezhny
Fix For: 3.3.0.M1
5 tests in JSF component failed with the same error in tearDown() method:
>>> org.jboss.tools.jsf.test.JsfAllTests.junit.framework.TestSuite@a6aae0 1.235 1
>>> org.jboss.tools.jsf.text.ext.test.JsfTextExtAllTests.org.jboss.tools.jsf.text.ext.test.JSF2CSSStylesheetOpenOnTest 2.778 1
>>> org.jboss.tools.jsf.text.ext.test.JsfTextExtAllTests.org.jboss.tools.jsf.text.ext.test.JSF2CCAttrsOpenOnTest 0.612 1
>>> org.jboss.tools.jsf.test.JsfAllTests.org.jboss.tools.jsf.model.pv.test.JsfJbide7975Test 2.943 2
>>> org.jboss.tools.jsf.text.ext.test.JsfTextExtAllTests.org.jboss.tools.jsf.text.ext.test.JSF2MessagesOpenOnTest 3.496 2
Error Message
Problems encountered while deleting resources.
Stacktrace
org.eclipse.core.internal.resources.ResourceException: Problems encountered while deleting resources.
at org.eclipse.core.internal.resources.Resource.delete(Resource.java:800)
at org.eclipse.core.internal.resources.Project.delete(Project.java:344)
at org.jboss.tools.test.util.ResourcesUtils.deleteProject(ResourcesUtils.java:206)
at org.jboss.tools.test.util.ProjectImportTestSetup.tearDown(ProjectImportTestSetup.java:85)
at junit.extensions.TestSetup$1.protect(TestSetup.java:24)
at junit.framework.TestResult.runProtected(TestResult.java:128)
at junit.extensions.TestSetup.run(TestSetup.java:27)
at junit.framework.TestSuite.runTest(TestSuite.java:232)
at junit.framework.TestSuite.run(TestSuite.java:227)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
at junit.extensions.TestSetup$1.protect(TestSetup.java:23)
at junit.framework.TestResult.runProtected(TestResult.java:128)
at junit.extensions.TestSetup.run(TestSetup.java:27)
at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83)
at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months
[JBoss JIRA] Created: (JBIDE-8873) Many tests in Seam component failed with the same error in tearDown() method
by Victor Rubezhny (JIRA)
Many tests in Seam component failed with the same error in tearDown() method
----------------------------------------------------------------------------
Key: JBIDE-8873
URL: https://issues.jboss.org/browse/JBIDE-8873
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jsp/jsf/xml source editing, Seam, testing
Affects Versions: 3.3.0.M1
Reporter: Victor Rubezhny
Assignee: Victor Rubezhny
Fix For: 3.3.0.M1
Some Seam component tests are throwing the Exceptions from tearDown() method (mostly on ResourceException occuring while cleaning up the resources) even if the test itself successfully pased.
This results in many failed tests which are actually non-failing.
For ecample:
org.eclipse.core.internal.resources.ResourceException: Problems encountered while deleting resources.
at org.eclipse.core.internal.resources.Resource.delete(Resource.java:800)
at org.eclipse.core.internal.resources.Project.delete(Project.java:352)
at org.jboss.tools.seam.core.test.project.facet.AbstractSeamFacetTest.tearDown(AbstractSeamFacetTest.java:134)
at org.jboss.tools.seam.core.test.project.facet.Seam2FacetInstallDelegateTest.tearDown(Seam2FacetInstallDelegateTest.java:93)
at org.jboss.tools.seam.core.test.project.facet.Seam20XFacetTestSuite201GA$Seam2FacetInstallDelegateTestSetup.tearDown(Seam20XFacetTestSuite201GA.java:42)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months
[JBoss JIRA] Created: (JBIDE-8789) rg.jboss.tools.jsf.test.validation.JSF2ComponentsValidatorTest.testJSF2ComponentsValidator() failure.
by Alexey Kazakov (JIRA)
rg.jboss.tools.jsf.test.validation.JSF2ComponentsValidatorTest.testJSF2ComponentsValidator() failure.
-----------------------------------------------------------------------------------------------------
Key: JBIDE-8789
URL: https://issues.jboss.org/browse/JBIDE-8789
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jsp/jsf/xml source editing
Affects Versions: 3.3.0.M1
Reporter: Alexey Kazakov
Assignee: Alexey Kazakov
Fix For: 3.3.0.M1
IMarker creation time without line calculating: 76
Tests run: 49, Failures: 4, Errors: 0, Skipped: 0, Time elapsed: 106.077 sec <<< FAILURE!
testJSF2ComponentsValidator(org.jboss.tools.jsf.test.validation.JSF2ComponentsValidatorTest) Time elapsed: 0.795 sec <<< FAILURE!
junit.framework.AssertionFailedError: null
at junit.framework.Assert.fail(Assert.java:47)
at junit.framework.Assert.assertTrue(Assert.java:20)
at junit.framework.Assert.assertTrue(Assert.java:27)
at org.jboss.tools.jsf.test.validation.JSF2ComponentsValidatorTest.testJSF2ComponentsValidator(JSF2ComponentsValidatorTest.java:70)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months
[JBoss JIRA] Created: (JBIDE-8638) 6 failing tests for JSF
by Nick Boldt (JIRA)
6 failing tests for JSF
------------------------
Key: JBIDE-8638
URL: https://issues.jboss.org/browse/JBIDE-8638
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JSF
Affects Versions: 3.3.0.M1
Reporter: Nick Boldt
Assignee: Alexey Kazakov
Priority: Blocker
Blocks downstream components from being able to build.
Tests have been failing for several builds (as many as 16!) now:
http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.component--jst...
>>><<< org.jboss.tools.jst.css.test.CSSAllTests.testEditorViewSelection
>>><<< org.jboss.tools.jst.text.ext.test.JstTextExtAllTests.testCSSStylesheetOpenOn
>>><<< org.jboss.tools.jst.text.ext.test.JstTextExtAllTests.testCSSClassOpenOn
>>><<< org.jboss.tools.jst.jsp.test.JstJspAllTests.testJstJspJbide1585
>>><<< org.jboss.tools.jst.jsp.test.JstJspAllTests.testJstJspJbide1641
>>><<< org.jboss.tools.jst.jsp.test.JstJspAllTests.testSelectionBarCommandState
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months
[JBoss JIRA] Created: (JBIDE-8459) I18nValidator creates invalid error messages
by Snjezana Peco (JIRA)
I18nValidator creates invalid error messages
--------------------------------------------
Key: JBIDE-8459
URL: https://issues.jboss.org/browse/JBIDE-8459
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JSF
Affects Versions: 3.3.x
Reporter: Snjezana Peco
Assignee: Alexey Kazakov
This issue can be reproduced by creating a Seam EAR project. The Web project will contain xhtml errors.
The problem is because I18nValidator is declared as a V2 validator, but doesn't implement the org.eclipse.wst.xml.core.internal.validation.eclipse.Validator.validate method.
org.eclipse.wst.xml.core.internal.validation.eclipse.Validator is executed with the default indicatNoGrammar value 1 (a warning) which throws errors.
A solution is to implement the Validator.validate method or set indicateNoGrammar to 0 (none).
BTW A validator by the name JSF2 Components Validator already exists.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months
[JBoss JIRA] Created: (JBIDE-8431) There are weired Externalization Problems on XHTML files.
by Alexey Kazakov (JIRA)
There are weired Externalization Problems on XHTML files.
---------------------------------------------------------
Key: JBIDE-8431
URL: https://issues.jboss.org/browse/JBIDE-8431
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jsp/jsf/xml source editing
Affects Versions: 3.3.0.M1
Reporter: Alexey Kazakov
Assignee: Maxim Areshkau
Priority: Critical
Fix For: 3.2.0.M1
1. Create JSF2 project using New JSF Project wizard (I haven't tried JSF1.2)
2. See the problem view. There are a lot of Externalization Problems such as:
- Attribute "xmlns:f" must be declared for element type "html".
- The content of element type "html" is incomplete, it must match "(head,body)".
- The content of element type "td" must match "(p|h1|h2|h3|h4|h5|h6|div|ul|ol|dl|menu|dir|pre|hr|blockquote|address|center|noframes|isindex|fieldset|table|form|a|br|span|bdo|object|applet|img|map|iframe|tt|i|b|big|small|u|s|strike|font|basefont|em|strong|dfn|code|q|sub|sup|samp|kbd|var|cite|abbr|acronym|input|select|textarea|label|button|ins|del|script|noscript)".
- etc.
3. If I open any file with the problems in VPE then the markers disappear.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months