[richfaces-issues] [JBoss JIRA] (RF-13582) Revert the core package re-factoring
[
https://issues.jboss.org/browse/RF-13582?page=com.atlassian.jira.plugin.s...
]
Jiří Štefek commented on RF-13582:
----------------------------------
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.
Revert the core package re-factoring
------------------------------------
Key: RF-13582
URL: https://issues.jboss.org/browse/RF-13582
Project: RichFaces
Issue Type: Task
Security Level: Public(Everyone can see)
Affects Versions: 4.5.0.Alpha3
Reporter: Brian Leathem
Assignee: Michal Petrov
Labels: needs-qe
Fix For: 4.5.0.Alpha3
Original Estimate: 3 hours
Remaining Estimate: 3 hours
To improve compatibility with RichFaces 4.3, the package re-factorings introduced should
be reverted. These include (but are not limited to):
* .servlet (PushServlet, ResourceServlet)
* .push.cdi (@PUsh)
* .push. (TopicContext)
* FileUploadException
A good test for this would be to compile and run the RichFaces 4.3 showcase and metamer
samples against RichFaces 4.5 looking for failures.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)