In Maven 3, if the <encoding> configuration parameter or the "project.build.sourceEncoding" property is not set, the compiler emits a warning like below:

> File encoding has not been set, using platform encoding UTF-8, i.e. build is platform dependent!

However since Java 18, the default encoding in a JVM is fixed to UTF-8, i.e. is no longer platform-dependent [1]. Consequently, above warning is no longer true except on Java 17 (the minimal version required by Maven 4). Is there any objection to remove the warning when Maven is run on Java 18 or later?

    Martin

[1]https://openjdk.org/jeps/400

Reply via email to