[
https://issues.apache.org/jira/browse/MYFACES-4526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17645293#comment-17645293
]
Werner Punz commented on MYFACES-4526:
--------------------------------------
note if you still need 18n use:
```xml
<h:outputScript pr:nonce="test123" name="faces-i18n.js" library="myfaces"
target="head"/>
```
respectively
```
<h:outputScript pr:nonce="test123" name="jsf-i18n.js" library="myfaces"
target="head"/>
```
The i18n part is deprecated and will be phased out when we move to the new
typescript codebase!
> Reduction of jsf.js build artifacts for 2.3 and 2.3-Next and Main
> -----------------------------------------------------------------
>
> Key: MYFACES-4526
> URL: https://issues.apache.org/jira/browse/MYFACES-4526
> Project: MyFaces Core
> Issue Type: Improvement
> Affects Versions: 2.3.10, 2.3-next-M7, 4.0.0-RC2
> Reporter: Werner Punz
> Assignee: Werner Punz
> Priority: Major
> Fix For: 2.3.11, 2.3-next-M8, 4.0.0-RC3
>
>
> We have introduced in the new codebase reduced build artifacts.
> Given that in 4.0 we use mapping files, we reduced the artifactos to a
> production and development faces.js file. Also the i18n was dropped because
> it was never used.
> Now, most of this makes sense also for the older codebase despite not having
> map files.
> The source still can be traced back in development due to the readability, but
> more important, can phase out i18n into a separate file (if still needed) and
> then reduce the file size signifcantly.
> Also that we we can get rid of all the extra config params like minimum,
> compressed-full etc... which are plainly confusing.
> This also will be rolled into the stable branch for 2.3 since we decided to
> sync the js codebases. So synching the js builds and resources also makes
> sense.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)