Chore/82: Migrate the build tool from maven to gradle

[ursjoss]

Resolves #82

[ursjoss]

As a first introduction, I like that you want to centralize the plugin management in buildSrc. I would, however, use a different style:

In buildSrc I'd create a Plugins.kt file and declare the plugins like this:

import org.gradle.kotlin.dsl.PluginDependenciesSpecScope
import org.gradle.kotlin.dsl.kotlin
import org.gradle.kotlin.dsl.version
import org.gradle.plugin.use.PluginDependencySpec

fun PluginDependenciesSpecScope.kotlinJvmPlugin(): PluginDependencySpec =
        kotlin("jvm") version Lib.kotlinVersion

fun PluginDependenciesSpecScope.kotlinSpringPlugin(): PluginDependencySpec =
        id("plugin.spring") version Lib.kotlinVersion

// etc.

I really like this approach, it's much more concise. However, I did not get it to work. The files in buildSrc don't seem to see the relevant scopes. Maybe we can have another look together next week.

Thanks for the spike review!

I pushed the change that fixes running scipamato-core, by the way.

[jcornaz]

Arf, Indeed.

My proposed change does not seem possible. The plugins block get a special treatment by gradle and is evaluated very early, even before the import statements of the script (because it defines what can be imported).

It prevents a lot of possible abstraction for applying the plugins. I'll have to play more with it to figure out what's the best solution.

[jcornaz]

It looks nice to me.

The build seems almost simple compared to the complexity of the project, so I'd call that a success.

It worked also well for me (I tried the tasks check, :core-web:bootRun and :public-web:bootRun)

[ursjoss]

@jcornaz Many thanks for your review!