[
https://issues.apache.org/jira/browse/MYFACES-4706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17925014#comment-17925014
]
Werner Punz commented on MYFACES-4706:
--------------------------------------
We have basically 2 codebases
* 4.x and 5.x are exactly identical ( new typescript codebase)
* 2.x are the old one 2.3-next are the old one with the legacy support ripped
out
* and 3.x is the old one with the jakarta namespace and minor refactorings!
the new typescript codebase also can support older jsf versions, because my
original intention was to replace the old code entirely, but it was decided
not to drag the new codebase into the existing branches due to customer support
concerns, which I understand. Hence this weird 3.x state was the result which
is 2x with jakarta but not entirely!
I hope this clears things up!
> Sync jsf.js code between 2.3 and 3.0
> ------------------------------------
>
> Key: MYFACES-4706
> URL: https://issues.apache.org/jira/browse/MYFACES-4706
> Project: MyFaces Core
> Issue Type: Bug
> Affects Versions: 3.0.2
> Reporter: Volodymyr Siedlecki
> Assignee: Werner Punz
> Priority: Major
>
> MYFACES-4522 synced up the javascript code between 2.3 and 2.3-next.
> However, 2.3 and 3.0 branches are basically the same. Therefore, the changes
> to 2.3 should be applied to 3.0. Support-wise, it would be easier since
> they would share the same code base.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
