New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
plugin 1.5.5 uses platform encoding for filtering resources #305
Comments
good catch! I created a PR to capture the property #306 Note that resources are just copied, filtering is disabled. |
Really, haven't been able to find anything to disable the messages, the code is pretty straight forward, nothing weird, no config files, nothing... Also modifying the logger is not possible and I don't like it anyway. After all of this, I have sent a message to the mailing list, let's see how it goes. |
Turns out, there was a new release of the We go from
to
@ecki, @mojavelinux if it's fine for you, I'd upgrade the version in the same PR #306 and close this issue with it. |
Fine with me. I think it is less confusing when the encoding would be the right one, but I agree that it probably does not apply. |
… (#306) * if set, uses project.build.sourceEncoding for resource filtering * upgraded maven-filtering to 3.1.1 to reduce console messages
Since 1.5.5 (as opposed to 1.5.3) the
process-asciidoc
goal will also copy (filtered) resources. It prints:Where
Cp1252
is my (Windows) platform encoding but not the encoding I have configured for the POM via<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
(debug output confirms it is set).I guess it is not that critical as most of those resources are not filtered anyway, but it does look like it is missing to define and propagate a
<encoding>
configuration (to resource copy as well as potential asciidoc file encoding?).Env: Maven 3.5.0 on Windows 10 x64 german with Java 1.8.0_141 with explicite asciidoctorj 1.5.6 and jruby 9.1.8.0.
The text was updated successfully, but these errors were encountered: