[
https://issues.jboss.org/browse/RF-13114?page=com.atlassian.jira.plugin.s...
]
Lukáš Fryč edited comment on RF-13114 at 8/21/13 3:00 PM:
----------------------------------------------------------
We must make sure that the RF 4.5 components' javascripts sources won't conflict
with RF 5 ones and vice-versa - resource names are different, however at javascript level,
objects will conflict mainly on {{RichFaces.ui}} object.
I have two ideas how to resolve that:
* components from RF 4.5 references resources in RF 5.0
** what shall we do when component will be replaced?
* we will prepare new namespaces for RF 4.5 components: {{RichFaces.ui4}}
Let's discuss possible resolutions first.
was (Author: lfryc):
We must make sure that the RF 4.5 components' javascripts sources won't
conflict with RF 5 ones and vice-versa - resource names are different, however at
javascript level, objects will conflict mainly on {{RichFaces.ui}} object.
I have two ideas how to resolve that:
* components from RF 4.5 references resources in RF 5.0
** what shall we do when component will be replaced?
* we will prepare new namespaces for RF 4.5 components: {{RichFaces.ui4}}
PoC: port RichFaces 4.5 UI Components to work with RichFaces 5
--------------------------------------------------------------
Key: RF-13114
URL:
https://issues.jboss.org/browse/RF-13114
Project: RichFaces
Issue Type: Task
Security Level: Public(Everyone can see)
Reporter: Lukáš Fryč
Assignee: Michal Petrov
Fix For: 5.0.0.Alpha2
Original Estimate: 1 week
Remaining Estimate: 1 week
* open branches in own fork of
** richfaces5 (master)
** richfaces-components (4.5.x)
** richfaces-showcase (master)
* modifications required
** change RF5 namespace ->
http://richfaces.org/core
** change parents/bom in components 4.5 to depend on RF5 framework / build-bom
*** remove all dependencies on 4.3.x (4.3.3-SNAPSHOT)
** change Java API of Components 4.5 to depend on RF5 Core API
** use the RF5 and RF4.5 UI Components in Showcase branch (4.5.0-SNAPSHOT)
--
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