gradle-plugin: changes after checking the publication

[rachelcarmena]

Goal

Solve the problems that have been found when publishing the plugin into Gradle repository:

• Redefined the plugin twice with ArrowKotlinGradleSubplugin.kt.
• Remove the artifact of compiler-plugin from the artifact of gradle-plugin. It couldn't be used in that way.
• Remove the use of the path ${project.rootDir}/modules/meta/arrow-meta-prototype/compiler-plugin/build/libs/compiler-plugin.jar
• Remove hardcoded versions to facilitate the release processes.

How to test it

When merging this pull request, the plugin will be published automatically with the version 0.10.3-rc-2 (the current published version is 0.10.3-rc-1).

Note

Gradle Plugin offers 2 options:

• Use the plugins DSL

plugins {
    id "io.arrow-kt.arrow" version "0.10.3-rc-2"
}

• Using the legacy plugin application:

buildscript {
    repositories {
        maven { url "https://plugins.gradle.org/m2/" }
    }
    dependencies {
        classpath "io.arrow-kt:gradle-plugin:0.10.3-rc-2"
    }
}

apply plugin: "io.arrow-kt.arrow"

However, in our case, we must document that it's only possible to use the second one, because it's necessary to include the repository to find compiler-plugin dependency which is in oss.jfrog.org right now:

buildscript {
    repositories {
        maven { url "https://plugins.gradle.org/m2/" }
        maven { url 'https://oss.jfrog.org/artifactory/oss-snapshot-local/' }
    }
    dependencies {
        classpath "io.arrow-kt:gradle-plugin:0.10.3-rc-2"
    }
}

apply plugin: "io.arrow-kt.arrow"

Otherwise, compiler-plugin will be searched in Gradle Plugins repository.

[raulraja]

Thanks @rachelcarmena !