[JBoss JIRA] Created: (RFPL-1176) Update hudson builds for new 4.0 branches
by Jay Balunas (JIRA)
Update hudson builds for new 4.0 branches
-----------------------------------------
Key: RFPL-1176
URL: https://issues.jboss.org/browse/RFPL-1176
Project: RichFaces Planning
Issue Type: Task
Security Level: Public (Everyone can see)
Components: build, QE, site
Reporter: Jay Balunas
Assignee: Prabhat Jha
Priority: Critical
Fix For: 4.0.0.Final
We need to update our hudson jobs based on the new branches for 4.0, and 4.next.
/trunk is now for 4.1.0-SNAPSHOT
/branches/4.0.X is for 4.0.0.Final, and then for any 4.0.1-SNAPSHOT work.
We should likely have a set for each of these.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 8 months
[JBoss JIRA] Created: (RFPL-1374) List shuttle component requirements planning for 4.X
by Jay Balunas (JIRA)
List shuttle component requirements planning for 4.X
----------------------------------------------------
Key: RFPL-1374
URL: https://issues.jboss.org/browse/RFPL-1374
Project: RichFaces Planning
Issue Type: Task
Security Level: Public (Everyone can see)
Components: components
Reporter: Jay Balunas
Assignee: Ilya Shaikovsky
Fix For: 4.1.0.Milestone1
Discussions around the migration/implementation of the various list shuttle components.
One of the reasons that these components did not get migrated is because we wanted to eliminate the converters, and other parts of them that made the components over complicated.
We need to capture this information on the wiki and begin discussions.
--
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: (RFPL-1188) Fix unstable test - TestRichDropDownMenu.testPopupWidth
by Lukas Fryc (JIRA)
Fix unstable test - TestRichDropDownMenu.testPopupWidth
-------------------------------------------------------
Key: RFPL-1188
URL: https://issues.jboss.org/browse/RFPL-1188
Project: RichFaces Planning
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: QE
Affects Versions: 4.0.0.CR1
Environment: JBoss 6 Final
Mojarra 2.0.3-b05
Reporter: Lukas Fryc
Assignee: Pavol Pitonak
Fix For: 4.0.0.Final
java.lang.AssertionError: Width of menu expected:<150px> but was:<155px>
at org.testng.Assert.fail(Assert.java:89)
at org.testng.Assert.failNotEquals(Assert.java:443)
at org.testng.Assert.assertEquals(Assert.java:113)
at org.testng.Assert.assertEquals(Assert.java:134)
at org.richfaces.tests.metamer.ftest.richDropDownMenu.TestRichDropDownMenu.testPopupWidth(TestRichDropDownMenu.java:275)
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.testng.internal.MethodHelper.invokeMethod(MethodHelper.java:643)
at org.testng.internal.Invoker.invokeMethod(Invoker.java:559)
at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:723)
at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1027)
at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:137)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:121)
at org.testng.TestRunner.runWorkers(TestRunner.java:1030)
at org.testng.TestRunner.privateRun(TestRunner.java:709)
at org.testng.TestRunner.run(TestRunner.java:579)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:331)
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:326)
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:288)
at org.testng.SuiteRunner.run(SuiteRunner.java:193)
at org.testng.TestNG.createAndRunSuiteRunners(TestNG.java:910)
at org.testng.TestNG.runSuitesLocally(TestNG.java:879)
at org.testng.TestNG.run(TestNG.java:787)
at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:74)
at org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:92)
at org.apache.maven.surefire.Surefire.run(Surefire.java:177)
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.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:345)
at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1009)
--
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: (RFPL-1468) Test rich:validator as wrapper around components
by Lukáš Fryč (JIRA)
Test rich:validator as wrapper around components
------------------------------------------------
Key: RFPL-1468
URL: https://issues.jboss.org/browse/RFPL-1468
Project: RichFaces Planning
Issue Type: Task
Security Level: Public (Everyone can see)
Components: QE
Affects Versions: 4.0.0.Final
Reporter: Lukáš Fryč
Assignee: Pavol Pitonak
We are using rich:validator namely for components:
{code:XML}
<h:inputText ...>
<rich:validator />
</h:inputText>
<h:inputText ...>
<rich:validator />
</h:inputText>
{code}
but it would be good to verify that rich:validator is also working when wrapping more components:
{code:XML}
<rich:validator>
<h:inputText ... />
<h:inputText ... />
</rich:validator>
{code}
Rewrite current rich:validator sample and tests to use wrapped usage for all kinds of components.
--
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: (RFPL-1475) Manage additions of new skins
by Lukáš Fryč (JIRA)
Manage additions of new skins
-----------------------------
Key: RFPL-1475
URL: https://issues.jboss.org/browse/RFPL-1475
Project: RichFaces Planning
Issue Type: Task
Security Level: Public (Everyone can see)
Affects Versions: 4.0.0.Final
Reporter: Lukáš Fryč
Assignee: Jay Balunas
Current skins in 4.x are basically clones of 3.x which is good for backward compatibility.
But we need also new skins which would better align with requirements of modern web designs.
We need to mockup 1-2 new skins to show what is possible with RF skinning capability.
We may need to consider using CSS3 + techniques for keeping compatibility across browsers.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months