April 2014 - richfaces-planning-issues

[JBoss JIRA] (RFPL-2264) Create tests for @rows in tables

by Jiří Štefek (JIRA)

[ https://issues.jboss.org/browse/RFPL-2264?page=com.atlassian.jira.plugin.... ] Jiří Štefek resolved RFPL-2264. ------------------------------- Fix Version/s: 4.3.7 Resolution: Done Resolved with commit https://github.com/richfaces/richfaces-qa/commit/da99f74f589773853d5ca070... > Create tests for @rows in tables > -------------------------------- > > Key: RFPL-2264 > URL: https://issues.jboss.org/browse/RFPL-2264 > Project: RichFaces Planning > Issue Type: Task > Security Level: Public(Everyone can see) > Components: QE > Affects Versions: 4.2.2.Final > Reporter: Pavol Pitonak > Assignee: Jiří Štefek > Fix For: 4.3.7 > > > Review Metamer tests for iteration components (a4j:repeat, rich:dataTable, rich:extendedDataTable, rich:collapsibleSubTable, rich:dataGrid, rich:list) if there are tests/samples using @rows in render attibute. Create new Se2 tests if none exist. You will find more info about @rows function in Component Reference [1] > [1] http://docs.jboss.org/richfaces/4.2.X/4.2.2.Final/Component_Reference/en-... -- 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

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RFPL-3242) metamer: almost all validation samples are not working on Tomcat

by Jiří Štefek (JIRA)

[ https://issues.jboss.org/browse/RFPL-3242?page=com.atlassian.jira.plugin.... ] Jiří Štefek commented on RFPL-3242: ----------------------------------- This should be fixed in JSF 2.2.7 ([JAVASERVERFACES-3183|https://java.net/jira/browse/JAVASERVERFACES-3183]). > metamer: almost all validation samples are not working on Tomcat > ---------------------------------------------------------------- > > Key: RFPL-3242 > URL: https://issues.jboss.org/browse/RFPL-3242 > Project: RichFaces Planning > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: QE > Environment: Tomcat 7.0.50 > Mojarra > Reporter: Jiří Štefek > Assignee: Jiří Štefek > Fix For: 5-Future > > > Works on AS 7.1, EAP 6.1, WildFly, Glassfish 3 and 4, but not on Tomcat. Worked in 5.0.0.Aplha2. > Occurs in all validation samples (for each input component), in both CSV and JSR-303 validations. > No errors are visible on the server side nor in browser console. -- 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

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RFPL-3046) Review Sonar reports

by Matej Novotny (JIRA)

[ https://issues.jboss.org/browse/RFPL-3046?page=com.atlassian.jira.plugin.... ] Matej Novotny commented on RFPL-3046: ------------------------------------- I made some investigation and the results are following: * There are 2 RF projects at the moment ** ['RichFaces Parent master'|http://sonar.mw.lab.eng.bos.redhat.com/sonar/dashboard/index/org.richfaces:richfaces-parent:master] is RF 5 project, fully working ** ['RichFaces Parent origin/master'|http://sonar.mw.lab.eng.bos.redhat.com/sonar/dashboard/index/org.richfaces:richfaces-parent:origin/master] is RF 4 project, outdated, there is no Jenkins job connected to it * New projects (eg. new RF 4 project) can be pushed via Jenkins (as post build action - see [this|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/RichFaces/view...]) which has installed plugin for Sonar (accordingly to Mojo article [here|https://mojo.redhat.com/docs/DOC-191202]). ** I tried to create a new [job|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/RichFaces/view/...] for RF 4 to replace the outdated one but so far I cannot make it work * We have read-only access to Sonar reports which is the major problem because: ** There are sets of [rules|http://sonar.mw.lab.eng.bos.redhat.com/sonar/rules_configuration/in...] which Sonar uses to detect quality of code, these are chosen and we cannot change them (there is 500+ rules used in current filter) ** We cannot mark some issues as 'false positive' so every time we would check the reports the same issues would pop-up over and over again *** For instance some code in demos does not meet quality requirement and Sonar detects this, however it is not really a problem as it is there for the sake of simplicity ** Cannot assign people to issues directly via Sonar ** Unability to change issue level (that is 'warning', 'blocker', 'major') results in some issues (for us maybe not so crucial) being marked with high priority ** The result of such extensive scan (given the rules used) is 3500+ issues found which is quite a lot and it is difficult to determine important issues since even amongst 'Major' issues there is almost 2000 of them * Code coverage: ** Sonar only reports on unit test coverage which is not really useful for us ** Mojo [article|https://mojo.redhat.com/docs/DOC-191202] claims it to be possible to execute integration tests, but one needs to use JaCoCo to generate results and Sonar then only shows them, this would be very difficult since we can only use Sonar via Jenkins and we have separate projects for tests and project itself => in theory it is possible to see integration test coverage with our setup but it would be very difficult to achieve and probably not so rewarding ** Sonar must have a plugin to display integration test coverage and I haven't found out whether we have it or not Summary: * Not suitable to be used for every release since the same issues (false-positive) would be displayed * However we can use these results for a one-time code improvement (but that requires quite a lot of time to determine which issues are to be corrected and which not) ** Certain issues are interesting and probably worth fixing BUT they are hard to locate amongst loads of other issues (we would need to choose only few probably) ** I will discuss this with [~ppitonak] and create relevant issues if we decide to track it * I will try to make the RF 4 repository tested by Sonar as well so I can see the results there (to see if there are as many issues as in RF 5) That is about what I found, I will add/edit comment if I find out anything else. > Review Sonar reports > -------------------- > > Key: RFPL-3046 > URL: https://issues.jboss.org/browse/RFPL-3046 > Project: RichFaces Planning > Issue Type: Task > Security Level: Public(Everyone can see) > Components: QE > Affects Versions: 5.0.0.Alpha1 > Reporter: Pavol Pitonak > Assignee: Matej Novotny > Fix For: 5-Future > > > Review Sonar reports, decide which warnings are important and either fix them or create RF issues for them. > Find a way how to exclude rules which are not importat for us. > http://sonar.mw.lab.eng.bos.redhat.com/sonar/dashboard/index/5878 -- 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

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (RFPL-3283) RichFaces 4.3.6 Release

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RFPL-3283?page=com.atlassian.jira.plugin.... ] Brian Leathem resolved RFPL-3283. --------------------------------- Resolution: Done > RichFaces 4.3.6 Release > ----------------------- > > Key: RFPL-3283 > URL: https://issues.jboss.org/browse/RFPL-3283 > Project: RichFaces Planning > Issue Type: Task > Security Level: Public(Everyone can see) > Components: release > Affects Versions: 4.3.6 > Reporter: Brian Leathem > Assignee: Michal Petrov > Priority: Blocker > Fix For: 4.3.6 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > RichFaces version: {{4.3.6.Final}} > RichFaces tag: {{4.3.6.20140404.Final}} > Metamer tag: {{4.3.6.20140404.Final}} > Shared Stage: https://repository.jboss.org/nexus/content/groups/staging/ > Private stage: > Tags in repositories: > *Release Notes:* > ---- > More information can be found in RichFaces 4.X release testing process document [2]. > [1] http://docs.jboss.org/jbossas/6/JSF_Guide/en-US/html_single/index.html#ch... > [2] https://community.jboss.org/wiki/Richfaces4Xreleasetestingprocess -- 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

10 years

1
0
0 / 0

[JBoss JIRA] (RFPL-3294) Integrate the release branch back to master

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RFPL-3294?page=com.atlassian.jira.plugin.... ] Brian Leathem updated RFPL-3294: -------------------------------- Summary: Integrate the release branch back to master (was: Integrate the release branch back to master/develop) > Integrate the release branch back to master > ------------------------------------------- > > Key: RFPL-3294 > URL: https://issues.jboss.org/browse/RFPL-3294 > Project: RichFaces Planning > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: release > Affects Versions: 4.3.6 > Reporter: Brian Leathem > Assignee: Michal Petrov > Fix For: 4.3.6 > > -- 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

10 years

1
0
0 / 0

[JBoss JIRA] (RFPL-3294) Integrate the release branch back to master/develop

by Michal Petrov (JIRA)

[ https://issues.jboss.org/browse/RFPL-3294?page=com.atlassian.jira.plugin.... ] Michal Petrov resolved RFPL-3294. --------------------------------- Resolution: Done Marking as done, though I was only working on master branch and didn't create the release and develop branches. > Integrate the release branch back to master/develop > --------------------------------------------------- > > Key: RFPL-3294 > URL: https://issues.jboss.org/browse/RFPL-3294 > Project: RichFaces Planning > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: release > Affects Versions: 4.3.6 > Reporter: Brian Leathem > Assignee: Michal Petrov > Fix For: 4.3.6 > > -- 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

10 years

1
0
0 / 0

[JBoss JIRA] (RFPL-3304) Update RF jira releases

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RFPL-3304?page=com.atlassian.jira.plugin.... ] Brian Leathem resolved RFPL-3304. --------------------------------- Resolution: Done > Update RF jira releases > ----------------------- > > Key: RFPL-3304 > URL: https://issues.jboss.org/browse/RFPL-3304 > Project: RichFaces Planning > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: release > Affects Versions: 4.3.6 > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.3.6 > > -- 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

10 years

1
0
0 / 0

[JBoss JIRA] (RFPL-3302) Make project site announcements, and forum announcements live

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RFPL-3302?page=com.atlassian.jira.plugin.... ] Brian Leathem resolved RFPL-3302. --------------------------------- Resolution: Done > Make project site announcements, and forum announcements live > ------------------------------------------------------------- > > Key: RFPL-3302 > URL: https://issues.jboss.org/browse/RFPL-3302 > Project: RichFaces Planning > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: release > Affects Versions: 4.3.6 > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.3.6 > > -- 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

10 years

1
0
0 / 0

[JBoss JIRA] (RFPL-3303) Tweet, post, other announcements

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RFPL-3303?page=com.atlassian.jira.plugin.... ] Brian Leathem resolved RFPL-3303. --------------------------------- Resolution: Done > Tweet, post, other announcements > -------------------------------- > > Key: RFPL-3303 > URL: https://issues.jboss.org/browse/RFPL-3303 > Project: RichFaces Planning > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: release > Affects Versions: 4.3.6 > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.3.6 > > -- 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

10 years

1
0
0 / 0

[JBoss JIRA] (RFPL-3301) Make blog live

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RFPL-3301?page=com.atlassian.jira.plugin.... ] Brian Leathem resolved RFPL-3301. --------------------------------- Resolution: Done > Make blog live > -------------- > > Key: RFPL-3301 > URL: https://issues.jboss.org/browse/RFPL-3301 > Project: RichFaces Planning > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: release > Affects Versions: 4.3.6 > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.3.6 > > -- 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

10 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

richfaces-planning-issues April 2014