https://kotlinlang.org logo
Channels
100daysofcode
100daysofkotlin
100daysofkotlin-2021
advent-of-code
aem
ai
alexa
algeria
algolialibraries
amsterdam
android
android-architecture
android-databinding
android-studio
androidgithubprojects
androidthings
androidx
androidx-xprocessing
anime
anko
announcements
apollo-kotlin
appintro
arabic
argentina
arkenv
arksemdevteam
armenia
arrow
arrow-contributors
arrow-meta
ass
atlanta
atm17
atrium
austin
australia
austria
awesome-kotlin
ballast
bangladesh
barcelona
bayarea
bazel
beepiz-libraries
belgium
benchmarks
berlin
big-data
books
boston
brazil
brikk
budapest
build
build-tools
bulgaria
bydgoszcz
cambodia
canada
carrat
carrat-dev
carrat-feed
chicago
chile
china
chucker
cincinnati-user-group
cli
clikt
cloudfoundry
cn
cobalt
code-coverage
codeforces
codemash-precompiler
codereview
codingame
codingconventions
coimbatore
collaborations
colombia
colorado
communities
competitive-programming
competitivecoding
compiler
compose
compose-android
compose-desktop
compose-hiring
compose-ios
compose-mp
compose-ui-showcase
compose-wear
compose-web
confetti
connect-audit-events
corda
cork
coroutines
couchbase
coursera
croatia
cryptography
cscenter-course-2016
cucumber-bdd
cyprus
czech
dagger
data2viz
databinding
datascience
dckotlin
debugging
decompose
decouple
denmark
deprecated
detekt
detekt-hint
dev-core
dfw
docs-revamped
dokka
domain-driven-design
doodle
dsl
dublin
dutch
eap
eclipse
ecuador
edinburgh
education
effective-kotlin
effectivekotlin
emacs
embedded-kotlin
estatik
event21-community-content
events
exposed
failgood
fb-internal-demo
feed
firebase
flow
fluid-libraries
forkhandles
forum
fosdem
fp-in-kotlin
framework-elide
freenode
french
fritz2
fuchsia
functional
funktionale
gamedev
ge-kotlin
general-advice
georgia
geospatial
german-lang
getting-started
github-workflows-kt
glance
godot-kotlin
google-io
gradle
graphic
graphkool
graphql
graphql-kotlin
graviton-browser
greece
grpc
gsoc
gui
hackathons
hacktoberfest
hamburg
hamkrest
helios
helsinki
hexagon
hibernate
hikari-cp
hire-me
hiring
hiring-french
hongkong
hoplite
http4k
hungary
hyderabad
image-processing
india
indonesia
inkremental
intellij
intellij-plugins
intellij-tricks
internships
introduce-yourself
io
ios
iran
israel
istanbulcoders
italian
jackson-kotlin
jadx
japanese
jasync-sql
java-to-kotlin-refactoring
javadevelopers
javafx
javalin
javascript
jdbi
jhipster-kotlin
jobsworldwide
jpa
jshdq
juul-libraries
jvm-ir-backend-feedback
jxadapter
k2-early-adopters
kaal
kafka
kakao
kalasim
kapt
karachi
karg
karlsruhe
kash_shell
kaskade
kbuild
kdbc
kgen-doc-tools
kgraphql
kinta
klaxon
klock
kloudformation
kmdc
kmm-español
kmongo
knbt
knote
koalaql
koans
kobalt
kobweb
kodein
kodex
kohesive
koin
koin-dev
komapper
kondor-json
kong
kontent
kontributors
korau
korean
korge
korim
korio
korlibs
korte
kotest
kotest-contributors
kotless
kotlick
kotlin-asia
kotlin-beam
kotlin-by-example
kotlin-csv
kotlin-data-storage
kotlin-foundation
kotlin-fuel
kotlin-in-action
kotlin-inject
kotlin-latam
kotlin-logging
kotlin-multiplatform-contest
kotlin-mumbai
kotlin-native
kotlin-pakistan
kotlin-plugin
kotlin-pune
kotlin-roadmap
kotlin-samples
kotlin-sap
kotlin-serbia
kotlin-spark
kotlin-szeged
kotlin-website
kotlinacademy
kotlinbot
kotlinconf
kotlindl
kotlinforbeginners
kotlingforbeginners
kotlinlondon
kotlinmad
kotlinprogrammers
kotlinsu
kotlintest
kotlintest-devs
kotlintlv
kotlinultimatechallenge
kotlinx-datetime
kotlinx-files
kotlinx-html
kotrix
kotson
kovenant
kprompt
kraph
krawler
kroto-plus
ksp
ktcc
ktfmt
ktlint
ktor
ktp
kubed
kug-leads
kug-torino
kvision
kweb
lambdaworld_cadiz
lanark
language-evolution
language-proposals
latvia
leakcanary
leedskotlinusergroup
lets-have-fun
libgdx
libkgd
library-development
lincheck
linkeddata
lithuania
london
losangeles
lottie
love
lychee
macedonia
machinelearningbawas
madrid
malaysia
mathematics
meetkotlin
memes
meta
metro-detroit
mexico
miami
micronaut
minnesota
minutest
mirror
mockk
moko
moldova
monsterpuzzle
montreal
moonbean
morocco
motionlayout
mpapt
mu
multiplatform
mumbai
munich
mvikotlin
mvrx
myndocs-oauth2-server
naming
navigation-architecture-component
nepal
new-mexico
new-zealand
newname
nigeria
nodejs
norway
npm-publish
nyc
oceania
ohio-kotlin-users
oldenburg
oolong
opensource
orbit-mvi
osgi
otpisani
package-search
pakistan
panamá
pattern-matching
pbandk
pdx
peru
philippines
phoenix
pinoy
pocketgitclient
polish
popkorn
portugal
practical-functional-programming
proguard
prozis-android-backup
pyhsikal
python
python-contributors
quasar
random
re
react
reaktive
realm
realworldkotlin
reductor
reduks
redux
redux-kotlin
refactoring-to-kotlin
reflect
refreshversions
reports
result
rethink
revolver
rhein-main
rocksdb
romania
room
rpi-pico
rsocket
russian
russian_feed
russian-kotlinasfirst
rx
rxjava
san-diego
science
scotland
scrcast
scrimage
script
scripting
seattle
serialization
server
sg-user-group
singapore
skia-wasm-interop-temp
skrape-it
slovak
snake
sofl-user-group
southafrica
spacemacs
spain
spanish
speaking
spek
spin
splitties
spotify-mobius
spring
spring-security
squarelibraries
stackoverflow
stacks
stayhungrystayfoolish
stdlib
stlouis
strife-discord-lib
strikt
students
stuttgart
sudan
swagger-gradle-codegen
swarm
sweden
swing
swiss-user-group
switzerland
talking-kotlin
tallinn
tampa
teamcity
tegal
tempe
tensorflow
terminal
test
testing
testtestest
texas
tgbotapi
thailand
tornadofx
touchlab-tools
training
tricity-kotlin-user-group
trójmiasto
truth
tunisia
turkey
turkiye
twitter-feed
uae
udacityindia
uk
ukrainian
uniflow
unkonf
uruguay
utah
uuid
vancouver
vankotlin
vertx
videos
vienna
vietnam
vim
vkug
vuejs
web-mpp
webassembly
webrtc
wimix_sentry
wwdc
zircon
Powered by
Title
e

eekboom

12/10/2019, 12:31 PM
After converting a build.gradle to Kotlin, I get “Unresolved reference: compile”. How do you set common dependencies from the parent project?
t

Thiago Nerys

12/10/2019, 12:32 PM
try
implementation
instead of
compile
e

eekboom

12/10/2019, 12:32 PM
No, same error. (But of course, good advice in general to use “implementation” rather than “compile”.)
t

Thiago Nerys

12/10/2019, 12:42 PM
guess it's gradle version
e

eekboom

12/10/2019, 12:43 PM
Woah. Very interesting. I am on latest 6.0.1
The only way I am able to make it work is by adding this in front of it
val compile by configurations
Hm, is your root project also using the “java” plugin?
t

Thiago Nerys

12/10/2019, 12:45 PM
Root project.
import org.jetbrains.kotlin.gradle.tasks.KotlinCompile

plugins {
   kotlin("jvm") version Versions.kotlin
   id("org.springframework.boot") version Versions.spring
   id("org.jetbrains.kotlin.plugin.spring") version Versions.kotlin
   id("io.spring.dependency-management") version Versions.springDependencyManagement
}

allprojects {
   repositories {
      mavenCentral()
   }

   tasks {
      withType(KotlinCompile::class).all {
         kotlinOptions {
            jvmTarget = "11"
            freeCompilerArgs = listOf("-Xjsr305=strict")
         }
      }
   }
}

subprojects {
   plugins.withType<JavaPlugin> {
      dependencies {
         compile("org.slf4j:sllf4j-api")
         implementation("org.slf4j:sllf4j-api")
      }
   }
}

dependencies {
   implementation(project(":integration"))
   runtime(project(":implementation"))

   implementation(kotlin("stdlib-jdk8", version = Versions.kotlin))
   implementation(kotlin("reflect", version = Versions.kotlin))

   implementation("org.springframework.boot:spring-boot-starter-web") {
      /* Excluding Tomcat dependency */
      exclude(module = "spring-boot-starter-tomcat")
   }
   implementation("org.springframework.boot:spring-boot-starter-undertow")
}
e

eekboom

12/10/2019, 12:49 PM
So your root project has `kotlin("jvm") version Versions.kotlin`and I think that’s why it works for you. If I add
plugins { id("java") …
it also works for me.
Which is very strange, because it really does add the dependencies to the subprojects (they can use classes from the dependency just fine).
t

Thiago Nerys

12/10/2019, 12:51 PM
Can you declare the java plugin in the root project with apply false?
e

eekboom

12/10/2019, 12:52 PM
gradle won’t let me do that:
Error resolving plugin [id: ‘java’, apply: false]
> Plugin ‘java’ is a core Gradle plugin, which is already on the classpath. Requesting it with the ‘apply false’ option is a no-op.
e

eskatos

12/10/2019, 1:44 PM
If the root project has no configuration named
compile
then there’s no static accessor in its build script. This is expected, see <https://docs.gradle.org/current/userguide/kotlin_dsl.html#type-safe-accessors> In that case you should use string references instead:
subprojects {
  plugins.withType<JavaPlugin> {
      dependencies {
         "compile"("org.slf4j:sllf4j-api")
         "implementation"("org.slf4j:sllf4j-api")
      }
   }
}
Note the double quotes.
e

eekboom

12/10/2019, 1:58 PM
Thanks for the answer! What really confuses me: Why does it actually work when the root project has a “compile” configuration? After all it needs to add the dependency to the sub project’s “compile” configuration. However, it really works at runtime. So what am I missing?
And isn’t there a way to make gradle aware of the actual subprojects’ configurations? There is already a `withType<JavaPlugin>`around it - but that does not help. Neither does `configure<JavaPluginConvention> {`help 😞
e

eskatos

12/10/2019, 2:03 PM
The type-safe accessors are generated for model elements that exist after applying the
plugins {}
block. That’s why
withType<JavaPlugin> {}
or
configure<JavaPluginConvention> {}
won’t help. Those accessors are Kotlin extension functions, in that case on the
DependencyHandler
type. They are static. That’s why they are usable on the
DependencyHandler
of sub projects in a
subprojects {}
block. Tradeoffs 🤷‍♂️
e

eekboom

12/10/2019, 2:15 PM
Thanks!
This is also a nice way to do it. It basically does the same, refer to the configuration by name.
e

eekboom

12/10/2019, 2:24 PM
Yeah, I think it is a little nice, even though it really is a glorified string based access, right.
What I still don’t understand is why it works if the root project itself has the Java plugin. Why don’t the dependencies get added to the root project’s configuration only?
e

eskatos

12/10/2019, 2:28 PM
Because the Kotlin extension is static. In other words it applies to a type, not an instance.
e

eekboom

12/10/2019, 2:28 PM
Oh yeah, of course! Thanks again!
👍 1
e

eskatos

12/10/2019, 2:29 PM
So,
dependencies {
    compile("foo:foo:1.0.")
}
subprojects {
    dependencies {
        compile("foo:foo:1.0.")
    }
}
it’s the same Kotlin function
fun DependencyHandler.compile(dep: String)
(simplified version) but applied to different
DependencyHandler
instances. In the first case to the root project, in the second case to each subprojects.