update to apache configurations2. load properties files with default utf-8 encoding

[ancho]

This is an update to apache commons configuration 2.7 which is up to date and much more configurable than 1.10.

You can now configure the encoding that should be used loading the properties file in a fluent way.

This PR makes #624 obsolete. But without the original PR we wouldn't even know that 1.10 had an encoding issue.

The only thing that is missing:

• add cli option (--prop-encoding) to configure property encoding that should be used

[coveralls]

Coverage increased (+0.3%) to 82.945% when pulling 4d32d38 on ancho:update/apache-configurations into 24722a6 on jbake-org:master.

[ancho]

What's wrong with windows builds and utf-8?

Test on appveyor fails with

ConfigUtilTest > shouldLoadPropertiesWithUtf8Encoding() FAILED
    java.lang.AssertionError: 
    Expecting:
     <"????????Properties??(Property value in Chinese will let property `site.about` missing due to Apache Configuration implementation.)">
    to contain:
     <"中文属性使用默认Properties编�?"> 
        at org.jbake.app.configuration.ConfigUtilTest.shouldLoadPropertiesWithUtf8Encoding(ConfigUtilTest.java:323)

But the properties file is utf-8

file C:\projects\jbake\jbake-core\src\test\resources\fixture\jbake.properties
C:\projects\jbake\jbake-core\src\test\resources\fixture\jbake.properties: UTF-8 Unicode text

hmmm....is this java.io (UTF8) vs. java.nio (UTF-8)?
https://docs.oracle.com/javase/8/docs/technotes/guides/intl/encoding.doc.html

[ancho]

@jonbullock , @manikmagar
Ok. I give up. I'm to stupid fixing the appveyor windows builds. Any ideas?

[ancho]

All right. Setting jvm parameter file.encoding to UTF-8 for windows solves the issue.
./gradlew -Dfile.encoding=UTF-8 -i check
I will cleanup/sqash the mess.

[manikmagar]

Looks good to me.

[jonbullock]

👍