Skip to content
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

Native image charset encoding UTF-8 #1971

Closed
richsanram opened this issue Apr 10, 2019 · 6 comments
Closed

Native image charset encoding UTF-8 #1971

richsanram opened this issue Apr 10, 2019 · 6 comments
Milestone

Comments

@richsanram
Copy link

When quarkus-maven-plugin is used to build a native image, the resulting binary cannot support UTF-8 characters.

I resolved this setting file.encoding property by hand in the command:

docker run -v /path/example/target:/project:z --rm quay.io/quarkus/centos-quarkus-native-image:graalvm-1.0.0-rc15 -J-Dfile.encoding=UTF-8 -J-Djava.util.logging.manager=org.jboss.logmanager.LogManager -H:InitialCollectionPolicy='com.oracle.svm.core.genscavenge.CollectionPolicy$BySpaceAndTime' -jar example-1.0-SNAPSHOT-runner.jar -J-Djava.util.concurrent.ForkJoinPool.common.parallelism=1 -H:+PrintAnalysisCallTree -H:-AddAllCharsets -H:EnableURLProtocols=http,https --enable-all-security-services -H:-SpawnIsolates -H:+JNI --no-server -H:-UseServiceLoaderFeature -H:+StackTrace

@limadelrey
Copy link

Any update on this @richsanram?

@gsmet
Copy link
Member

gsmet commented Nov 13, 2019

I'm closing as we don't have enough information to understand what the issue is.

If you encounter the issue yourself, please open a new issue with the description of what the problem you're trying to solve is.

@gsmet gsmet closed this as completed Nov 13, 2019
@gsmet gsmet added the triage/out-of-date This issue/PR is no longer valid or relevant label Nov 13, 2019
@nhoughto
Copy link

nhoughto commented Jul 6, 2020

For those coming google, this appears the same as oracle/graal#2492

@gsmet
Copy link
Member

gsmet commented Jul 7, 2020

@jaikiran continuing here as I mistakenly posted in the GraalVM issue instead of this one.

I think your proposal is reasonable and we can add an option later if people ask for it. Maybe let's make it ready for our next CR so that people can complain early if it's an issue for them.

@jaikiran
Copy link
Member

jaikiran commented Jul 7, 2020

@gsmet, done #10527

@gsmet gsmet added this to the 1.7.0 - master milestone Jul 7, 2020
@gsmet gsmet removed the triage/out-of-date This issue/PR is no longer valid or relevant label Jul 7, 2020
@gsmet
Copy link
Member

gsmet commented Jul 7, 2020

This will be fixed in the upcoming 1.7 release.

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

No branches or pull requests

5 participants