[
https://issues.apache.org/jira/browse/MYFACES-4706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17912664#comment-17912664
]
Werner Punz commented on MYFACES-4706:
--------------------------------------
Yes give me a few days, I am as usual very busy with my days work. Question,
since the 3.0 codebase was derived from next, which basically is a decluttered
2.x codebase (aka 2.x codebase striped off from all the legaxy stuff like
blueberry support ie6 support) do you want to roll in the entire 2x codebase or
just the i18n?
Just asking. The codebase is modular anyway, next and 3.x is just a subset of
the 2.x codebase (the legacy parts were split off in separate classes, hence
getting rid of the "junk" was easy!
> 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)
