[ https://issues.jboss.org/browse/RF-13582?page=com.atlassian.jira.plugin.s... ] Jiří Štefek edited comment on RF-13582 at 6/19/14 6:48 AM: ----------------------------------------------------------- I have created a branch in qa repo for this. [This commit|https://github.com/richfaces/richfaces-qa/commit/5eab3f39145cf1bd6...] adds the RF 4.5 jars to Metamer and make it compilable, could you, please, check if I didn't something wrong? As you can see in the commit, there are just changes in rich components (not in core components). I've also run all tests for a4j components from this branch ([verified with this job|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/richfaces-x.y-me...], ignore the status JS API tests (different call of JS API function in RF 4.3 and 4.5 {{RichFaces.$}} X {{RichFaces.component}})) + manually verified {{queue}} and {{attachedQueue}} components (there are no WebDriver tests for them). From these results I can confirm that all a4j components works correctly in 4.3 Metamer with 4.5 components. was (Author: jstefek): I have created a branch in qa repo for this. [This commit|https://github.com/richfaces/richfaces-qa/commit/5eab3f39145cf1bd6...] adds the RF 4.5 jars to Metamer and make it compilable, could you, please, check if I didn't something wrong? As you can see in the commit, there are just changes in rich components. I've also run all tests for a4j components from this branch ([verified with this job|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/richfaces-x.y-me...], ignore the status JS API tests (different call of JS API function in RF 4.3 and 4.5 {{RichFaces.$}} X {{RichFaces.component}})) + manually verified {{queue}} and {{attachedQueue}} components (there are no WebDriver tests for them). From these results I can confirm that all a4j components works correctly. -- This message was sent by Atlassian JIRA (v6.2.6#6264)