thank you! 🙂

is there any way to make @JvmField default for a class/project?

sweet

why do you need this?

because my whole code I implement POJOS with final fields

and I have to add @JvmField to every single property now, instead of making this default

are getters/setters generated for

val

fields?

it seems so

only getters will be generated for

val

fields, this can be verified quite easy when checking the output bytecode

both getters and setters will be generated for `var`s 😉

Hi, there is unclear error

Cannot access 'm': it is protected in 'Abstr'

In the following code:

abstract class Abstr{
    protected abstract fun m()
}

class Child : Abstr(){
    private val subChild: Abstr = Child()

    override fun m() = subChild.m()// Error:(12, 18) Kotlin: Cannot access 'm': it is protected in 'Abstr'
}

Is it a bug? The question also was asked here: https://stackoverflow.com/questions/47015707/kotlin-cannot-access-protected-abstract-method/

does not sound like a bug, you’re trying to access a protected method from outside?

I need a map as a result

I have been thinking about storing this values in yaml file, but I do not need hierarchy, only key-value pair

@Greg Stepniewski The both classes in the same file. If I change property declaration from`subChild: Abstr` to

subChild: Child

, then it compiles ok

What about JSON?

I thing JSON is also an overhead

i just need smth like config file

My Customer Name = 123

parse into Map<String,int>

a properties files ?

I suppose I can;t write with spaces in properties file

@SerGnat that’s because Child extends the visibility of the method. So you can call the method on Child, but not Abstr I take that back. https://kotlinlang.org/docs/reference/visibility-modifiers.html This says it should still be protected.

What about yaml? It was made for config files

yes, but I am looking for yaml parser

@Greg Stepniewski Agree. But Abstr#m() should be visible for Child too

@SerGnat I did some tests and there is definitely a bug there somewhere, but I’m not sure exactly what the correct behaviour would be. The doc says

protected — same as private + visible in subclasses too

and my interpretation is that it should only allow subclasses to call superclass methods within the same instance, but I might be wrong

This guide shows quite different settings form what the wizard did: https://kotlinlang.org/docs/reference/using-maven.html E.g. it specifies

sourceDir

for the Kotlin plugin, should I do that? And why does it replace the execution for the java compiler plugin in the guide?

<!-- Replacing default-compile as it is treated specially by maven -->

How specially? What? What does that mean?

does it possible to write generic extension?

Yes:

fun <T> Iterable<T>.foo() = ...