[JBoss JIRA] Created: (JBIDE-8404) 2 failing tests in jsf.vpe
by Nick Boldt (JIRA)
2 failing tests in jsf.vpe
--------------------------
Key: JBIDE-8404
URL: https://issues.jboss.org/browse/JBIDE-8404
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JSF
Affects Versions: 3.2.0.Final
Reporter: Nick Boldt
Assignee: Alexey Kazakov
http://hudson.qa.jboss.com/hudson/job/jbosstools-3.2_stable_branch.compon...
org.jboss.tools.jsf.vpe.jsf.test.JsfAllTests.testCAforJSPFiles
Number of ca proposals shouldn't be a 0
org.jboss.tools.jsf.vpe.jstl.test.JstlAllTests.testRequestEncoding
Caused by: java.lang.NullPointerException
at org.eclipse.wst.sse.ui.internal.style.SemanticHighlightingReconciler.reconcile(SemanticHighlightingReconciler.java:115)
at org.eclipse.wst.sse.ui.internal.reconcile.DocumentRegionProcessor.endProcessing(DocumentRegionProcessor.java:119)
at org.eclipse.wst.sse.ui.internal.reconcile.DirtyRegionProcessor.run(DirtyRegionProcessor.java:682)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months
[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, 9 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, 9 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, 9 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, 9 months
[JBoss JIRA] Created: (JBIDE-7956) GWT integration cannot be installed
by Libor Zoubek (JIRA)
GWT integration cannot be installed
-----------------------------------
Key: JBIDE-7956
URL: https://issues.jboss.org/browse/JBIDE-7956
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, GWT
Affects Versions: 3.2.0.CR1
Environment: nightly update site zip 20101215-1434-H4-CR1
Reporter: Libor Zoubek
Assignee: Nick Boldt
Cannot complete the install because one or more required items could not be found.
When attempting to install GWT integration I get:
Software being installed: JBoss GWT Integration (Experimental) 1.0.0.v20101215-1434-H4-CR1 (org.jboss.tools.gwt.feature.feature.group 1.0.0.v20101215-1434-H4-CR1)
Missing requirement: JBoss Tools GWT (Experimental) 1.0.0.v20101215-1434-H4-CR1 (org.jboss.tools.gwt.core 1.0.0.v20101215-1434-H4-CR1) requires 'bundle com.google.gwt.eclipse.sdkbundle.2.1.0 [2.1.0,3.0.0)' but it could not be found
Cannot satisfy dependency:
From: JBoss GWT Integration (Experimental) 1.0.0.v20101215-1434-H4-CR1 (org.jboss.tools.gwt.feature.feature.group 1.0.0.v20101215-1434-H4-CR1)
To: org.jboss.tools.gwt.core [1.0.0.v20101215-1434-H4-CR1]
google updatesite is present at version
Google App Engine Java SDK 1.4.0 1.4.0.v201012021502 com.google.appengine.eclipse.sdkbundle.e36.feature.1.4.0.feature.group
Google Plugin for Eclipse 3.6 1.4.1.v201012170127 com.google.gdt.eclipse.suite.e36.feature.feature.group
Google Web Toolkit SDK 2.1.1 2.1.1.v201012170127 com.google.gwt.eclipse.sdkbundle.e36.feature.2.1.1.feature.group
looks like google have renamed features few days ago :-/
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months