Skip to content

Encode transformed properties files with specified Charset#819

Merged
johnrengelman merged 2 commits intoGradleUp:masterfrom
scottsteen:properties-transformer-charset
Mar 20, 2023
Merged

Encode transformed properties files with specified Charset#819
johnrengelman merged 2 commits intoGradleUp:masterfrom
scottsteen:properties-transformer-charset

Conversation

@scottsteen
Copy link
Copy Markdown

Currently, the content from any properties file that is passed through the PropertiesFileTransformer will have its output written into the jar encoded as ISO_8859_1. If the source file contains UTF-8 content, the output becomes corrupted.

This commit allows the buildscript to define the Charset to perform the transformation with.

Resolves #818

@scottsteen scottsteen force-pushed the properties-transformer-charset branch from f120f4b to d214b6f Compare February 10, 2023 14:47
Currently, the content from any properties file that is passed through
the `PropertiesFileTransformer` will have its output written into the
jar encoded as `ISO_8859_1`. If the source file contains UTF-8 content,
the output becomes corrupted.

This commit allows the buildscript to define the Charset to perform the
transformation with.
@scottsteen scottsteen force-pushed the properties-transformer-charset branch from d214b6f to 9bffd1e Compare February 13, 2023 12:29
@johnrengelman johnrengelman added this to the 8.1.1 milestone Mar 20, 2023
@johnrengelman johnrengelman merged commit 5aecf84 into GradleUp:master Mar 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

UTF-8 encoded content not output correctly by PropertiesFileTransformer

2 participants