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

Brian Leathem edited comment on RF-12802 at 8/16/13 4:39 PM:
-------------------------------------------------------------

Is there any progress on this issue?  It's blocking RF-12950.

---

Nevermind, progress is clearly being demonstrated in the relevant forum thread:
https://community.jboss.org/thread/230766
                
      was (Author: bleathem):
    Is there any progress on this issue?  It's blocking RF-12950.
                  
> 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
>             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
_______________________________________________
richfaces-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/richfaces-issues

Reply via email to