[
https://issues.jboss.org/browse/RF-12802?page=com.atlassian.jira.plugin.s...
]
Juraj Húska commented on RF-12802:
----------------------------------
We have finished the first round of the refactoring.
In this is the
[
last|https://github.com/richfaces/richfaces-qa/commit/6e8f58cac501848c614...]
commit I have added a showcase class for each page fragment. It is always in the package
with the specific fragment, and the the name pattern for it is {{*Showcase.java}}. I
wanted to showcase the high level API of each fragment in this way. It is how the end
non-rf tester should use the fragment.
I was wondering about adding such a piece of code to the component reference for each
component, so it can be reused.
Now, we would like to kindly ask the development team for a review.
Then we can proceed with JavaDoc or other refactorings.
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