Le 4/07/2017 à 14:08, Markus Koschany a écrit : > Maybe let's start with an upload to > experimental and we try it on some guinea pig javahelper packages first.
Why not but it looks like a lot of efforts for no gain (besides the satisfaction of compiling with a modern encoding, but that's not a feature with a visible impact for our users or on the maintenance). I'd rather focus on fixing the Java 9 issues. > Maybe the logic should be: IF NOT EXIST property encoding in pom.xml or > (IF EXIST debian/maven.properties AND debian/maven.properties CONTAINS > STRING project.build.sourceEncoding) SET encoding to UTF-8 For Maven projects this will fix nothing. If the project has UTF-8 encoded files and doesn't define project.build.sourceEncoding, the package already FTBFS on the builders and we should be aware of it. I think our Maven based packages are fine, they either have: - the source encoding defined in pom.xml - the source encoding defined in debian/maven.properties - no encoding specified but have only ASCII source files Setting a default encoding at the maven-debian-helper level will make no difference. __ This is the maintainer address of Debian's Java team <http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers>. Please use debian-j...@lists.debian.org for discussions and questions.