[
https://issues.apache.org/jira/browse/MYFACES-4522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17911043#comment-17911043
]
Werner Punz edited comment on MYFACES-4522 at 1/8/25 12:13 PM:
---------------------------------------------------------------
I have to look into it why it was phased out on 3.0... this was probably a
mistake, next had it phased out, I will look into it!
Should not be too hard to get i18n in again! It is just a code bloat for a non
standard feature which not really anyone uses, but nevertheless, I will look
into it!
was (Author: werpu):
I have to look into it why it was phased out on 3.0... this was probably a
mistake, next had it phased out, I will look into it!
Should not be too hard to get i18n in again!
> jsf.js sync the 2.3-next files back into 2.3
> --------------------------------------------
>
> Key: MYFACES-4522
> URL: https://issues.apache.org/jira/browse/MYFACES-4522
> Project: MyFaces Core
> Issue Type: Task
> Affects Versions: 2.3.10
> Reporter: Werner Punz
> Assignee: Werner Punz
> Priority: Major
> Fix For: 2.3.11
>
>
> We have had a ton of fixes in the old codebase which made it so far into
> 2.3-next and 4.0
> however given that 2.3 still is in active development we should sync those
> changes back into the 2.3 branch. Given 2.3-next and 2.3 share the same code
> on JS level, a simple diff should suffice instead of cherry picking every fix.
> I will make a single commit under this issue for 2.3
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
