[
https://issues.apache.org/jira/browse/MYFACES-4522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17644437#comment-17644437
]
Werner Punz commented on MYFACES-4522:
--------------------------------------
Btw. I also will use this opportunity to streamline the builds like we have it
in the new codebase.
>From now on we will only have development and production builds with no extra
>config parameters.
i18n will be phased out of those files, but still an 18n translation file will
be present which can be downloaded in a separate include. i18n will be phased
out entirely for the new codebase anyway, given that no one really needs it (I
have never gotten any feedback to it, and mojarra does not have it)
I will open a second issue for it and push the small changes for it next week!
> 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
>
> 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)
