Review new RichFaces sample application
---------------------------------------
Key: RFPL-435
URL: https://jira.jboss.org/jira/browse/RFPL-435
Project: RichFaces Planning
Issue Type: Task
Security Level: Public (Everyone can see)
Components: examples
Affects Versions: 3.3.3.CR1
Environment: JSF2, RichFaces 3.3.3.CR1, JBoss 6 M2
Reporter: Pavol Pitonak
Please review the following application based on JSF2 and RichFaces 3.3.3.CR1, deploy to JBoss 6 M2
http://anonsvn.jboss.org/repos/qa/people/ppitonak/richrates/
focus on
* web.xml - missing or unnecessary settings
* beans - scopes, dependency injection
* xhtml - template, validation of calendars, toolbar
* other
--
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
Define release process for 4.0.0
--------------------------------
Key: RFPL-445
URL: https://jira.jboss.org/jira/browse/RFPL-445
Project: RichFaces Planning
Issue Type: Task
Security Level: Public (Everyone can see)
Components: administration, build
Reporter: Jay Balunas
Assignee: Jay Balunas
Priority: Blocker
Fix For: 4.0.0.ALPHA2
The release process for the 4.0.X releases need to be defined, and take into account the time-box releases of future milestone releases.
--
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
CDK: publish schemas on the Internet
------------------------------------
Key: RFPL-167
URL: https://jira.jboss.org/jira/browse/RFPL-167
Project: RichFaces Planning
Issue Type: Task
Reporter: Nick Belaevski
Some ideas:
1. richfaces.org
2. Maven repository
3. Anonymous SVN
Need to make sure that proper versioning is provided for schema documents
--
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
Review existing components that might need to updated
-----------------------------------------------------
Key: RFPL-444
URL: https://jira.jboss.org/jira/browse/RFPL-444
Project: RichFaces Planning
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Reporter: Jay Balunas
--
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
Define migration process requirements
-------------------------------------
Key: RFPL-438
URL: https://jira.jboss.org/jira/browse/RFPL-438
Project: RichFaces Planning
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: administration, components
Reporter: Jay Balunas
Assignee: Jay Balunas
Fix For: 4.0.0.ALPHA2
--
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
MyFaces 2 integration
---------------------
Key: RFPL-603
URL: https://jira.jboss.org/browse/RFPL-603
Project: RichFaces Planning
Issue Type: Task
Security Level: Public (Everyone can see)
Components: build, QA
Affects Versions: 4.0.0.ALPHA2
Reporter: Nick Belaevski
Assignee: Nick Belaevski
Fix For: 4.0.0.M1
Integrate MyFaces 2.x into 4.x development & development. Currently Mojarra is being used, MyFaces should be configured and tested also.
--
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
richfaces-selenium: Implement failure catching mechanisms
---------------------------------------------------------
Key: RFPL-530
URL: https://jira.jboss.org/jira/browse/RFPL-530
Project: RichFaces Planning
Issue Type: Sub-task
Reporter: Lukas Fryc
Assignee: Lukas Fryc
There are several possibilities to watch the failures, which can be useful to track down, what happen with particular selenium build:
1. capture of screen
2. obtaining HTML source
3. obtaining recent network traffic
4. obtaining most recent selenium logs
This will need implement the proxy for command processor and/or testng listener,
the lot of functionality is already in place.
--
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