[
https://issues.apache.org/jira/browse/AVRO-2207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16672255#comment-16672255
]
ASF subversion and git services commented on AVRO-2207:
-------------------------------------------------------
Commit 26700949812e39f6ddedc63c53f8cb5562fd7f15 in avro's branch
refs/heads/master from [~arkadiusx]
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=2670094 ]
AVRO-2207: avro-maven-plugin: Using project.build.sourceEncoding as a encoding
for files generated from avdl/avpr
> avro-maven-plugin don't specify encoding for files generated from avdls and
> avprs
> ---------------------------------------------------------------------------------
>
> Key: AVRO-2207
> URL: https://issues.apache.org/jira/browse/AVRO-2207
> Project: Avro
> Issue Type: Bug
> Components: java
> Affects Versions: 1.8.2
> Reporter: Arek Burdach
> Priority: Major
>
> When someone generates source file from avdl/avpr, compiler uses system
> default encoding for output files. It can be different from this expected by
> project's compiler. It is quite usual thing that developers specify source
> encoding on project level using {{project.build.sourceEncoding}} property and
> expects that it will solve the problem.
> The problem doesn't exists when sources are generated from avsc. That
> implementation sets output encoding to this taken from
> {{project.build.sourceEncoding}}.
> Proposed solutions is to use the same behaviour in other two cases (avdl and
> avpr).
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
