[richfaces-issues] [JBoss JIRA] (RF-12802) Move page fragments from repository qa to richfaces5

[Brian Leathem (JIRA)]

    [ https://issues.jboss.org/browse/RF-12802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12809270#comment-12809270 ] 

Brian Leathem edited comment on RF-12802 at 10/3/13 4:59 PM:
-------------------------------------------------------------

A link to the commit that introduces a "showcase" of how to use the Page Fragments:
https://github.com/richfaces/richfaces-qa/commit/6e8f58cac501848c6143285db4a172b036ac15c6
----
I see now that [~jhuska] linked to this in his comment calling for a review.  I missed it.
                
      was (Author: bleathem):
    A link to the commit that introduces a "showcase" of how to use the Page Fragments:
https://github.com/richfaces/richfaces-qa/commit/6e8f58cac501848c6143285db4a172b036ac15c6
                  
> 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: Brian Leathem
>             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