November 2012 - richfaces-planning-issues

[JBoss JIRA] Created: (RFPL-1253) components: effects support to be added

by Ilya Shaikovsky (JIRA)

components: effects support to be added --------------------------------------- Key: RFPL-1253 URL: https://issues.jboss.org/browse/RFPL-1253 Project: RichFaces Planning Issue Type: Feature Request Security Level: Public (Everyone can see) Components: components Reporter: Ilya Shaikovsky Priority: Critical Fix For: 4.Next Need to review subj and define tasks (analysis, specifications, impls) That's are really big one and frequently asked ehcancement so should be carefully designed prior to impl. So RFPL created as initially that is really task for discussion and planning. Initially I'm thinking about some set of predefined effects which could be added by additional attributes for corresponding components events like: <panelMenuGroup expandEffect="rf.effects.slide"> ... which could be later expanded to use custom JS functions like mySlide to trigger some custom effect. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

4
5
0 / 0

[JBoss JIRA] Created: (RFPL-486) Consider during development and QE that exceptions and console diagnostic messages should be informative and has good spelling

by Ilya Shaikovsky (JIRA)

Consider during development and QE that exceptions and console diagnostic messages should be informative and has good spelling ------------------------------------------------------------------------------------------------------------------------------ Key: RFPL-486 URL: https://jira.jboss.org/jira/browse/RFPL-486 Project: RichFaces Planning Issue Type: Task Security Level: Public (Everyone can see) Components: CDK, components Affects Versions: 4.0.0.ALPHA1 Reporter: Ilya Shaikovsky Assignee: Jay Balunas Jay, we asked about that much times during 3.x development. And also have "improved diagnostic" as one of the goals for 4.x. Sometimes we have just not informative exceptions at all(them just not caught and re-thrown properly). E.g. indexOutOfBounds exception while just parsing attribute (really there should be message about wrong attribute value) Sometimes just English is not really good in message. E.g. "javax.faces.FacesException: Target pointed Attribute for of AjaxStatus component with id status not is AjaxContainer" in Ajax status. So think I could add to one of the core 4.x planning pages at wiki and then I think this should be assigned to Prabhat for inclusion into check list and considering during QE. WDYT? -- 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

11 years, 7 months

3
11
0 / 0

[JBoss JIRA] (RFPL-156) Setup project site containing standard reports

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RFPL-156?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RFPL-156: ------------------------------------ See JBQA-2837 > Setup project site containing standard reports > ---------------------------------------------- > > Key: RFPL-156 > URL: https://issues.jboss.org/browse/RFPL-156 > Project: RichFaces Planning > Issue Type: Task > Security Level: Public(Everyone can see) > Components: QE > Affects Versions: 4.0.0.Alpha2 > Reporter: Nick Belaevski > Assignee: Pavol Pitonak > Priority: Minor > Labels: review > > The following reports are necessary: > - Clover2 > - CPD > - PMD/Findbugs > - Dependencies report > - Checkstyle > - License checking plugin > - (?) > Historical reports generation is not a must but good to have -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (RFPL-156) Setup project site containing standard reports

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RFPL-156?page=com.atlassian.jira.plugin.s... ] Brian Leathem reassigned RFPL-156: ---------------------------------- Assignee: Pavol Pitonak Can you review this? Is it something we can easily do with the infrastructure we have in place? How about the sonatype sonar project? Would it be a good fit for this? > Setup project site containing standard reports > ---------------------------------------------- > > Key: RFPL-156 > URL: https://issues.jboss.org/browse/RFPL-156 > Project: RichFaces Planning > Issue Type: Task > Security Level: Public(Everyone can see) > Components: QE > Affects Versions: 4.0.0.Alpha2 > Reporter: Nick Belaevski > Assignee: Pavol Pitonak > Priority: Minor > Labels: review > > The following reports are necessary: > - Clover2 > - CPD > - PMD/Findbugs > - Dependencies report > - Checkstyle > - License checking plugin > - (?) > Historical reports generation is not a must but good to have -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (RFPL-156) Setup project site containing standard reports

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RFPL-156?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RFPL-156: ------------------------------- Component/s: QE (was: build) > Setup project site containing standard reports > ---------------------------------------------- > > Key: RFPL-156 > URL: https://issues.jboss.org/browse/RFPL-156 > Project: RichFaces Planning > Issue Type: Task > Security Level: Public(Everyone can see) > Components: QE > Affects Versions: 4.0.0.Alpha2 > Reporter: Nick Belaevski > Priority: Minor > Labels: review > > The following reports are necessary: > - Clover2 > - CPD > - PMD/Findbugs > - Dependencies report > - Checkstyle > - License checking plugin > - (?) > Historical reports generation is not a must but good to have -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (RFPL-571) Setup CDK schema documentation automated builds

by Nick Belaevski (JIRA)

Setup CDK schema documentation automated builds ----------------------------------------------- Key: RFPL-571 URL: https://jira.jboss.org/jira/browse/RFPL-571 Project: RichFaces Planning Issue Type: Task Security Level: Public (Everyone can see) Components: build, CDK Affects Versions: 4.0.0.ALPHA2 Reporter: Nick Belaevski Assignee: Nick Belaevski Fix For: 4.0.0.M1 -- 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

11 years, 7 months

3
7
0 / 0

[JBoss JIRA] (RFPL-156) Setup project site containing standard reports

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RFPL-156?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RFPL-156: ------------------------------- Summary: Setup project site containing standard reports (was: Setup project site containing standart reports) > Setup project site containing standard reports > ---------------------------------------------- > > Key: RFPL-156 > URL: https://issues.jboss.org/browse/RFPL-156 > Project: RichFaces Planning > Issue Type: Task > Security Level: Public(Everyone can see) > Components: build > Affects Versions: 4.0.0.Alpha2 > Reporter: Nick Belaevski > Priority: Minor > Labels: review > > The following reports are necessary: > - Clover2 > - CPD > - PMD/Findbugs > - Dependencies report > - Checkstyle > - License checking plugin > - (?) > Historical reports generation is not a must but good to have -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (RFPL-1128) Setup assembler for sandbox components

by Nick Belaevski (JIRA)

Setup assembler for sandbox components --------------------------------------- Key: RFPL-1128 URL: https://issues.jboss.org/browse/RFPL-1128 Project: RichFaces Planning Issue Type: Task Security Level: Public (Everyone can see) Components: build Reporter: Nick Belaevski Assignee: Jay Balunas Fix For: 4.Next -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

4
4
0 / 0

[JBoss JIRA] Created: (RFPL-965) Review JBoss manifest requirements and create tasks to match

by Jay Balunas (JIRA)

Review JBoss manifest requirements and create tasks to match ------------------------------------------------------------ Key: RFPL-965 URL: https://issues.jboss.org/browse/RFPL-965 Project: RichFaces Planning Issue Type: Task Security Level: Public (Everyone can see) Components: build Reporter: Jay Balunas Assignee: Jay Balunas Priority: Critical Fix For: 4.0.0.CR1 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

4
12
0 / 0

[JBoss JIRA] (RFPL-1467) @Test annotation param dependsOnMethods in Metamer's ftest causes IllegalStateException

by Jiří Štefek (JIRA)

[ https://issues.jboss.org/browse/RFPL-1467?page=com.atlassian.jira.plugin.... ] Jiří Štefek reassigned RFPL-1467: --------------------------------- Assignee: Pavol Pitonak (was: Jiří Štefek) Yes, this problem still occurs. It is not problem in TestNG, but in *MatrixConfigurator*. The method *intercept(List<IMethodInstance> methodInstances, ITestContext context)* (from *IMethodIntercepter*) works only with *methodInstances* which covers ??'... only methods that have no dependents and that don't depend on any other test methods ...'?? [from IMethodIntercepter], so the rest of methods, which can be recovered from context, is ignored. The *MatrixConfigurator* should be refactored. > @Test annotation param dependsOnMethods in Metamer's ftest causes IllegalStateException > --------------------------------------------------------------------------------------- > > Key: RFPL-1467 > URL: https://issues.jboss.org/browse/RFPL-1467 > Project: RichFaces Planning > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: QE > Environment: Metamer 4.1.0-snapshot, r.22501 > Reporter: Ján Jamrich > Assignee: Pavol Pitonak > Fix For: 5-Future > > > When tried set dependsOnMethods param to @Test annotation in Metamer's ftests, get IllegalStateException thrown from MatrixConfigurator. > There aren't any other methods annotated by @Test with dependsOnMethods param, so its possible that this issue is in Metamer longer time without being discovered. > By debugging observed that list of methods set to be executed by TestRunner depends on this param. In other word, when set dependsOnMethods param to @Test annotation - this method (on which was this param set to annotation) doesn't appear in list of methods being executed (LinkedList<Method> methods attribute of MatrixConfigurator). > This attribute is initialized in method > public List<IMethodInstance> intercept(List<IMethodInstance> methodInstances, ITestContext context) > which is called directly from org.testng.TestRunner, which give param List<IMethodInstance> methodInstances depending on dependsOnMethods param set to @Test annotation as well. > This behavior should be ok, since methods which are not depending on another else method should be executed first. > But what seems worse is that when run this again - for method anotated by @Test with param dependsOnMethod, then list of methods which going to be executed is empty - do no test method called. > And in case when all methods except one depends on another method, different exception is result of run testsuite: > Running TestSuite > org.apache.maven.surefire.booter.SurefireExecutionException: null; nested exception is java.lang.NullPointerException: null > java.lang.NullPointerException > at org.richfaces.tests.metamer.ftest.MetamerTestInfo.getConfigurationInfo(MetamerTestInfo.java:50) > at org.richfaces.tests.metamer.ftest.MetamerTestInfo.getConfigurationInfoInParenthesses(MetamerTestInfo.java:77) > at org.richfaces.tests.metamer.ftest.MetamerSeleniumLoggingTestListener.getMessage(MetamerSeleniumLoggingTestListener.java:35) > at org.jboss.test.selenium.listener.SeleniumLoggingTestListener.logStatus(SeleniumLoggingTestListener.java:82) > at org.jboss.test.selenium.listener.SeleniumLoggingTestListener.onTestFailure(SeleniumLoggingTestListener.java:55) > at org.testng.internal.Invoker.runTestListeners(Invoker.java:1634) > at org.testng.internal.Invoker.runTestListeners(Invoker.java:1618) > at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1101) > 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:62) > at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:141) > 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) > So this should be issue related to TestNG itself (current version 5.12.1), tried 5.13, but the same behavior. > There is stack trace: > java.lang.IllegalStateException: can't find more configured methods > at org.richfaces.tests.metamer.ftest.MatrixConfigurator.configureMethod(MatrixConfigurator.java:150) > at org.richfaces.tests.metamer.ftest.MatrixConfigurator.beforeInvocation(MatrixConfigurator.java:101) > at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:62) > at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:141) > at org.apache.maven.surefire.Surefire.run(Surefire.java:177) > at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:345) > at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1009) > ... Removed 22 stack frames -- 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, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

richfaces-planning-issues November 2012