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
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
a

Arjan van Wieringen

01/21/2023, 8:55 AM
Maybe another noob question here, but would it be possible for me to create a custom gradle plugin that does the following: • apply multiplatform, compose and publishing plugins • set some sensible defaults • add some basic dependencies The reason I want this is that I want to have one starting point for all my projects with all the versions correctly set. I then only want to apply this plugin to get started. Would the preferred way be a real Gradle plugin, or would it be possible in a precompiled script plugin?
a

Adam S

01/21/2023, 9:02 AM
yeah, that’s super easy to do precompiled script plugins are very easy to make, so I’d recommend that first If you’re working in a large organisation and you have tonnes of projects that you want to make sure are aligned, then you can think about publishing a plugin with these conventions - but even then it’s usually a lot of hassle for not much benefit (imho)
for version alignment, you could also consider • version catalogs (
libs.versions.toml
), so all the dependencies and versions are in one file • version platforms (Java Platform Plugin), which is kind of like making your own BOM, so you can define dependencies without versions in projects and the Platform will align them https://docs.gradle.org/current/userguide/platforms.html
a

Arjan van Wieringen

01/21/2023, 9:07 AM
Thanks for your reply. The precompiled script plugin is easy to publish as well right?
a

Adam S

01/21/2023, 9:09 AM
I think so, but I’ve never done it. It’s relatively easy to convert from
my-convention.gradle.kts
to
MyConvention.kt
a

Adam S

01/21/2023, 10:16 AM
yes sorry, my previous message was ambiguous. I should have said “Even if it’s not possible, it’s relatively easy to convert them”
v

Vampire

01/21/2023, 10:17 AM
Precompiled script plugins are real plugins. They are just some syntactic sugar on top.
And yes, what you describe is exactly the recommended idiomatic approach. Having a convention plugin that does what you want and then apply just that.
a

Arjan van Wieringen

01/21/2023, 1:17 PM
Ah, I have refactored everything to use the libs.version.toml, but sadly this can not be used in a (precompiled) plugin.
I think I maybe overcomplicated stuff. My goal was to create a gradle plugin which I can use in a target project which sets up a lot of basic dependencies and plugins to develop a compose desktop application. This means: compose plugin, coroutines dependencies, some serialization plugin, proper Kotlin version etc etc.
v

Vampire

01/21/2023, 3:08 PM
Ah, I have refactored everything to use the libs.version.toml, but sadly this can not be used in a (precompiled) plugin.
Well, that's only partly correct. You can use the string-y untyped API to access the version catalog. Or you can use the hack-around I described in the according issue on GitHub.
I think I maybe overcomplicated stuff. My goal was to create a gradle plugin which I can use in a target project which sets up a lot of basic dependencies and plugins to develop a compose desktop application. This means: compose plugin, coroutines dependencies, some serialization plugin, proper Kotlin version etc etc.
As I said, that's exactly the idiomatic way and is called convention plugin. Whether you implement it in a standalone project, in an included build, in
buildSrc
, as "real plugin", as precompiled script plugin, ... is not important. 🙂
a

Arjan van Wieringen

01/21/2023, 3:46 PM
Thanks! I will look into that.
@Vampire Maybe I am overlooking it, but where is this Github issue you mentioned?
a

Arjan van Wieringen

01/21/2023, 4:29 PM
Great. Thanks. Sadly it doesn't really work in a plugin block for now, if I am correct because the Groovy DSL is more restrictive
v

Vampire

01/21/2023, 4:30 PM
For Groovy DSL you do not need my hack-around at all, but yeah, in plugins block it works in neither DSL in a precompiled script plugin
a

Arjan van Wieringen

01/21/2023, 4:30 PM
Damn 😞 So in a precompuled script plugin I can't enable a specific version of a plugin then.
v

Vampire

01/21/2023, 4:31 PM
Not in the
plugins
block. But you could probably use the legacy
apply
to do it.
a

Adam S

01/21/2023, 4:32 PM
if you add the plugin’s Maven coordinates (not the plugin ID) to
dependencies {}
in
buildSrc/build.gradle.kts
then when you apply the plugin in the pre-compiled script plugin, it will choose that version
and you can use
libs.versions.toml
in
buildSrc/build.gradle.kts
a

Arjan van Wieringen

01/21/2023, 4:33 PM
Okay, but will it pick the correct version when I publish the pre-compiled plugin and apply the plugin in a completely new project?
a

Adam S

01/21/2023, 4:40 PM
yes, I’m pretty sure it will. I’m a little uncertain because I don’t fully understand the Gradle mechanisms. I do know that Gradle generally recommends against applying a specific plugin, and instead leave that up to the plugin-consumer. https://docs.gradle.org/current/userguide/implementing_gradle_plugins.html#reacting_to_plugins
v

Vampire

01/21/2023, 4:57 PM
Ah, yeah, @Adam S is completely right of course. In a precompiled script plugin you cannot apply a plugin with version anyway, can you? Regarding letting the consumer decide, that's not really correct. If you want to configure a plugin in case it is applied, then you react to it. But you can of course apply a plugin with a specific version if you want that. It's just two different use-cases for a convention plugin.
s

Stylianos Gakis

01/22/2023, 11:51 PM
Here’s a great place to look at a project which does exactly what you are asking for and can copy basically the entire thing. https://github.com/android/nowinandroid/tree/main/build-logic One convention plugin example from in there which adds dependencies https://github.com/android/nowinandroid/blob/main/build-logic/convention/src/main/kotlin/AndroidFeatureConventionPlugin.kt And one convention plugin example which applies compose too https://github.com/android/nowinandroid/blob/main/build-logic/convention/src/main/kotlin/AndroidLibraryComposeConventionPlugin.kt
a

Arjan van Wieringen

01/23/2023, 6:43 PM
This is amazing. Thanks!