Bug#866845: libidw-java FTBFS: PropertyMapImpl.java:383: error: unmappable character for encoding ASCII

[Markus Koschany]

Am 03.07.2017 um 11:33 schrieb Emmanuel Bourg:
> Le 3/07/2017 à 11:19, Markus Koschany a écrit :
> 
>> Don't we have a way to say javahelper and maven-debian-helper default to
>> UTF-8 but existing overrides like project.build.sourceEncoding (Maven)
>> or export _JAVA_OPTIONS (javahelper) still continue to work and take
>> precedence over them?
> 
> For maven-debian-helper setting the project.build.sourceEncoding
> property from the command line will override the encoding specified by
> the pom.xml, so it isn't a good option.
> 
> For javahelper, jh_build only adds the encoding to the command line if
> it isn't defined in JH_JAVAC_OPTS, so the package can still override the
> default.

So if I understand correctly all pure javahelper packages are safe as
long as they have defined the encoding already? Well, for the rest,
let's try and fix it.

I don't understand the maven-debian-helper case though. The
project.build.sourceEncoding in my maven.properties file won't override
the new default UTF-8 value anymore?


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 963 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-java-maintainers/attachments/20170703/23de60a6/attachment.sig>