July 2012 - richfaces-planning-issues

[JBoss JIRA] Created: (RFPL-1593) Cover a4j:ajax listener attribute by UI tests

by Ján Jamrich (JIRA)

Cover a4j:ajax listener attribute by UI tests --------------------------------------------- Key: RFPL-1593 URL: https://issues.jboss.org/browse/RFPL-1593 Project: RichFaces Planning Issue Type: Feature Request Security Level: Public (Everyone can see) Environment: Metamer 4.1.0-M1 Reporter: Ján Jamrich There are lot of h:inputs with a4j:ajax examples (faces/components/a4jAjax/list.xhtml), where the "listener" attribute is not covered by selenium test. (hSelectBooleanCheckbox.xhtml, hSelectOneRadio.xhtml, hSelectOneListbox.xhtml - with tests: TestHSelectOneListbox, TestHSelectOneRadio). But its not complete list of Test. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (RFPL-1539) Split the user forums into a RichFaces3 and RichFaces 4 forum

by Brian Leathem (JIRA)

Split the user forums into a RichFaces3 and RichFaces 4 forum ------------------------------------------------------------- Key: RFPL-1539 URL: https://issues.jboss.org/browse/RFPL-1539 Project: RichFaces Planning Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Brian Leathem Fix For: 4.1.0.Final As the RF-4 codebase continues to diverge from the RF-3 codebase, many problems/bugs are fixed in RF-4 that are still encountered by RF-3 users. This makes it difficult to support questions in the user forums, as with the RF-3 codebase being frozen, the questions will tend to repeat, and confuse the situation with RF-4 users. To remedy this problem, I suggest splitting the existing User forum in two: a RichFaces-3 and a RichFaces-4 forum. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

3
5
0 / 0

[JBoss JIRA] Created: (RFPL-1592) Metamer - rich:graphValidator - attribute <groups> can't be set

by Jan Papousek (JIRA)

Metamer - rich:graphValidator - attribute <groups> can't be set ---------------------------------------------------------------- Key: RFPL-1592 URL: https://issues.jboss.org/browse/RFPL-1592 Project: RichFaces Planning Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.1.0.Milestone1 Environment: * RichFaces 4.1.0.20110805-M1 r.10246d45dddd1d2aa2034317d5a832394cc919f9 * Metamer 4.1.0.20110805-M1 r.22604 * Mojarra 2.1.3-FCS * Apache Tomcat 6.0.32 * OpenJDK Runtime Environment 1.6.0_22-b22 @ Linux * Firefox 3.6.19 @ Linux i686 (x86_64) Reporter: Jan Papousek When something else than null value is used to set the attribute groups, an error about converting string to class occurs. For example: /components/richGraphValidator/all.xhtml @171,70 groups="#{richGraphValidatorBean.attributes['groups'].value}": Cannot convert org.richfaces.tests.metamer.validation.groups.ValidationGroupBooleanInputs of type class java.lang.String to class [Ljava.lang.Class; -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (RFPL-1144) ConfigurationService: add unit tests for JNDI & property files support

by Nick Belaevski (JIRA)

ConfigurationService: add unit tests for JNDI & property files support ---------------------------------------------------------------------- Key: RFPL-1144 URL: https://issues.jboss.org/browse/RFPL-1144 Project: RichFaces Planning Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.0.0.CR1 Reporter: Nick Belaevski Assignee: Nick Belaevski Fix For: 4.Next Add unit tests for: * ConfigurationItemSource.webEnvironmentEntry * ConfigurationItemsBundle.propertiesFile() -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

3
2
0 / 0

[JBoss JIRA] Created: (RFPL-727) Metamer on Hudson: configure Code Coverage analysis

by Lukas Fryc (JIRA)

Metamer on Hudson: configure Code Coverage analysis --------------------------------------------------- Key: RFPL-727 URL: https://jira.jboss.org/browse/RFPL-727 Project: RichFaces Planning Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.0.0.Milestone1 Environment: Hudson Reporter: Lukas Fryc Assignee: Lukas Fryc Fix For: 4.0.0.CR1 Configure two new jobs Hudson, which will implement Code Coverage mechanisms integrated to Hudson/Maven environment: Investigate following options: Clover, Emma, Cobertura Configure following setups: 1. Metamer Ftest coverage of Metamer Application's code 2. Metamer Ftest coverage of RichFaces Framework code itself -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

5
12
0 / 0

[JBoss JIRA] Created: (RFPL-1370) Document 4.X release process including jira, and announcements, and schema updates

by Jay Balunas (JIRA)

Document 4.X release process including jira, and announcements, and schema updates ---------------------------------------------------------------------------------- Key: RFPL-1370 URL: https://issues.jboss.org/browse/RFPL-1370 Project: RichFaces Planning Issue Type: Task Security Level: Public (Everyone can see) Components: administration, build, site Reporter: Jay Balunas Assignee: Ilya Shaikovsky Priority: Minor Fix For: 4.0.1.Milestone1 We need to create a separate document from http://community.jboss.org/docs/DOC-15747?uniqueTitle=false which outlines our release procedure that we use with jira. Examples include https://issues.jboss.org/browse/RFPL-1256 We also need to add details on how to upload schemas, and create announcement on project site, and forums. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

5
9
0 / 0

[JBoss JIRA] Created: (RFPL-219) Update RichFaces jira guide to include information on vote and rejection of jira's

by Jay Balunas (JIRA)

Update RichFaces jira guide to include information on vote and rejection of jira's ---------------------------------------------------------------------------------- Key: RFPL-219 URL: https://jira.jboss.org/jira/browse/RFPL-219 Project: RichFaces Planning Issue Type: Task Components: administration, site Affects Versions: Site Reporter: Jay Balunas Priority: Minor Fix For: Site Need to update with information on voting, and why/how issues are rejected -- 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

13 years, 6 months

2
1
0 / 0

[JBoss JIRA] (RFPL-2085) Deploy showcase version 4.0 and 4.1 to Flex

by Lukáš Fryč (JIRA)

Lukáš Fryč created RFPL-2085: -------------------------------- Summary: Deploy showcase version 4.0 and 4.1 to Flex Key: RFPL-2085 URL: https://issues.jboss.org/browse/RFPL-2085 Project: RichFaces Planning Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.2.0.Final Reporter: Lukáš Fryč Assignee: Lukáš Fryč Fix For: 4.3.0.Tracking Each must have own application in Flex. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

2
5
0 / 0

[JBoss JIRA] Created: (RFPL-1509) Update sandbox process

by Jay Balunas (JIRA)

Update sandbox process ---------------------- Key: RFPL-1509 URL: https://issues.jboss.org/browse/RFPL-1509 Project: RichFaces Planning Issue Type: Task Security Level: Public (Everyone can see) Components: administration, site Reporter: Jay Balunas Fix For: 4.1.0.Final Now that we have moved to git, and are going to be integrating a component from the sandbox into the 4.1 release we need to get the sandbox process updated and easier to use. We should have a step by step guide, linking to how to create a component wiki, of how to get your component into the RichFaces sandbox. This would include forking sandbox, updating some sort of a descriptor file, updating the wiki, etc... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

5
6
0 / 0

[JBoss JIRA] Created: (RFPL-1461) Blog and publicize how the application was deployed

by Jay Balunas (JIRA)

Blog and publicize how the application was deployed --------------------------------------------------- Key: RFPL-1461 URL: https://issues.jboss.org/browse/RFPL-1461 Project: RichFaces Planning Issue Type: Sub-task Security Level: Public (Everyone can see) Components: administration, examples, site Reporter: Jay Balunas Assignee: Lukáš Fryč Fix For: 4.1.0.Milestone1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

5
7
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

richfaces-planning-issues July 2012