Move to gradle.

[portlek]

This will make our life easier when implementing #302
maven is relatively hard to add kotlin support, so it would be much more easier to make it in a Gradle environment.

[0dinD]

I don't see how this is related to #302 (which just seems to be a documentation issue), but maybe I have misunderstood what #302 is about?

maven is relatively hard to add kotlin support,

Kotlin support for what? You can already use Gradle with Kotlin to depend on AnvilGUI.

---

Whether AnvilGUI uses Maven or Gradle doesn't matter at all for the users of the library. In the end Maven and Gradle are compatible with each other when it comes to consuming dependencies.

So the decision to use Gradle for AnvilGUI seems to mostly be a matter of personal taste unless there is some specific Gradle feature that we want to use. I personally don't oppose moving to Gradle, so I trust whatever decision is made by the maintainers.

[portlek]

Kotlin support for what? You can already use Gradle with Kotlin to depend on AnvilGUI.

im not talking about that. i was talking about the #302 to make it easier to implement.

[0dinD]

Yeah I had just misunderstood what #302 was about, your argument makes sense now. It seems doable to build Kotlin code with Maven, but I would also not be surprised if Jetbrains has given the Gradle plugins for Kotlin more love than the Maven counterparts, so I trust your experience if you say that it's much easier in Gradle (I have not used Kotlin much, so I wouldn't know).

[0dinD]

Moving to Gradle seems like an implementation detail to me, for someone who uses AnvilGUI it won't matter whether we use Maven or Gradle. The simplicity of Maven is very appealing, so unless we have a strong reason to move to Gradle, I don't think it makes sense to switch. That matter can be discussed if and when such a reason comes along.