[
https://issues.jboss.org/browse/RF-12802?page=com.atlassian.jira.plugin.s...
]
Juraj Húska edited comment on RF-12802 at 9/9/13 5:12 AM:
----------------------------------------------------------
We are still in the process of Page Fragments refactoring, however it is coming to the
end.
Following actions need to be done to finish refactoring, so it can be reviewed by you
guys:
* finish refactoring of Metamer tests to the new API of: {{r:panelMenu}} and {{r:tree}}
* pair program the most complex refactoring of {{r:calendar}} and refactor tests
accordingly
* unify proposed {{Wait}} API for all page fragments
* unify {{AdvancedInteractions}} API for all page fragments
* after review of page fragments from you guys, complete Javadoc
I will cross particular action once it is completed.
was (Author: jhuska):
We are still in the process of Page Fragments refactoring, however it is coming to the
end.
Following actions need to be done to finish refactoring, so it can be reviewed by you
guys:
* finish refactoring of Metamer tests to the new API of: {{r:panelMenu}} and {{r:tree}}
* pair program the most complex refactoring of {{r:calendar}} and refactor tests
accordingly
* unify proposed {{Wait}} API for all page fragments
* unify {{AdvancedInteractions}} API for all page fragments
* after review of page fragments from you guys, complete Javadoc
I will cross the action once they are completed.
Move page fragments from repository qa to richfaces5
----------------------------------------------------
Key: RF-12802
URL:
https://issues.jboss.org/browse/RF-12802
Project: RichFaces
Issue Type: Task
Security Level: Public(Everyone can see)
Components: build/distribution
Affects Versions: 5.0.0.Alpha1
Reporter: Pavol Pitonak
Assignee: Juraj Húska
Fix For: 5.0.0.Alpha2
As discussed on community meeting on Feb 12, we should move page fragments for RichFaces
components to richfaces5 repository so that they are distributed with framework.
We should find out how to prepare them so that they are easy to use for community
members. RichFaces QE/dev need to test internals of components, community members will
probably test only high-level functionality of components. One possible solution would be
to create package "internal" in which there would be page fragments extending
those from "public" package. QE team would then use "internal"
implementations.
--
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