Allow private fields as properties

[Sxtanna]

Allowing for private fields would make usage from Kotlin less ugly.

In its current state, the library resolves all fields, private included, and just throws away fields that are inaccessible.

Simply inserting Field#setAccessible(true) above this line here:

ConfigMe/src/main/java/ch/jalu/configme/configurationdata/ConfigurationDataBuilder.java

Line 115 in 1084f43

return (Property<?>) field.get(null);

Will resolve this issue.

[ljacqu]

I don't have much experience with Kotlin—are there any other shortcomings that could be improved for Kotlin integration? I'd like to get a better picture as to maybe bundle a few improvements to facilitate usage from Kotlin.

[Sxtanna]

Aside from that, a benefit not only for Kotlin, but Java as well would be for the project to utilize the jetbrains annotations to mark nullability and contracts.

IntelliJ is able to infer some of them, but proper definition is always better.

[ljacqu]

As long as the field is static, it will be picked up by the default configuration data builder. Sample Kotlin code that will work with the next release:

import ch.jalu.configme.Comment
import ch.jalu.configme.SettingsHolder
import ch.jalu.configme.SettingsManagerBuilder
import ch.jalu.configme.properties.PropertyInitializer
import ch.jalu.configme.utils.Utils
import java.nio.file.Paths

fun main(args: Array<String>) {
    val path = Paths.get("./configme-kt-test.yml")
    Utils.createFileIfNotExists(path);

    val settings = SettingsManagerBuilder
        .withYamlFile(path)
        .configurationData(TitleSettings.javaClass)
        .create()

    println("App: ${settings.getProperty(TitleSettings.TITLE_TEXT)}")
}

object TitleSettings: SettingsHolder {

    @Comment("Demo")
    val TITLE_TEXT = PropertyInitializer.newProperty("title.text", "woof")

}

Previously, @JvmField was required.