Gradle plugin: fix --include-build workflow

By convention, gradle uses project name as artifactId, `project.group`
property for groupId and `project.version` for version.

This commit switches to this convention instead of configuring
publication tasks directly. It allows to easily substitute published
plugin with a plugin build locally by issuing

`./gradlew build --include-build ../kotlin-native`

in the dependent project.
This commit is contained in:
Aleksey Kladov
2017-05-24 14:43:48 +03:00
committed by ilmat192
parent 6116f24abc
commit fce134ee56
11 changed files with 5 additions and 5 deletions
+1 -1
View File
@@ -25,4 +25,4 @@ include ':runtime'
include ':common'
include ':backend.native:tests'
include ':tools:helpers'
include ':tools:gradle-plugin'
include ':tools:kotlin-native-gradle-plugin'
@@ -20,6 +20,9 @@ apply plugin: 'kotlin'
apply plugin: 'maven-publish'
apply plugin: 'com.jfrog.bintray'
group = 'org.jetbrains.kotlin'
version = konanVersion
// TODO: move this code to top level (the same for backend.native)
// Copied from backend.native
allprojects {
@@ -80,9 +83,6 @@ publishing {
publications {
gradlePlugin(MavenPublication) {
artifact jar
groupId 'org.jetbrains.kotlin'
artifactId 'kotlin-native-gradle-plugin'
version konanVersion
pom.withXml { XmlProvider xml ->
def stdlibDep = xml.asNode().appendNode("dependencies").appendNode("dependency")
stdlibDep.appendNode("groupId", "org.jetbrains.kotlin")
@@ -111,4 +111,4 @@ bintray {
override = project.hasProperty("override")
}
publications = ['gradlePlugin']
}
}