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
s

sdeleuze

05/25/2018, 10:46 AM
Question: why do I have to use
val shadowJar by tasks.getting(ShadowJar::class) { ... }
to exclude files with the shadow plugin instead of using
shadow { ... }
which provides a useless
ShadowExtension
lambda? Is the shadow plugin badly designed ? I see this kind of issue in various plugins so I would like to know what is the rationale behind this and understand that kind of issue and at what level this should be fixed ...
j

jlleitschuh

05/25/2018, 3:32 PM
The
extension
is usually considered the wa that you configure the entire plugin. The configuration that you put on the
extension
can cause the plugin to create various different tasks that are outside the scope of what any normal user would need to configure. Additionally, things configured on an extension might do things like cause multiple tasks to be created depending upon how it's configured. The configuration of the tasks with code like:
tasks.withType<ShadowJar> {
   // Some config here
}
It's more about configuring the logic specific to one part of a plugin's task execution. @eriwen any interest in chiming in here to add any additional information and/or a link to a Gradle doc that explains the differences better than I can?
e

eriwen

05/25/2018, 3:42 PM
Is the issue here that
val shadowJar by tasks.getting(ShadowJar::class)
is not intuitive? Jonathan has suggested an alternative that should work well. That said, I’m sure John Engelman has a good reason for having folks configure ShadowJar tasks instead of using an extension.
c

Czar

05/25/2018, 3:49 PM
do note, that code suggested by Jonathan will configure all tasks of that type, while
val shadowJar by...
approach will only configure task named "shadowJar". This may matter in multi-module projects.
my 2 cents:
tasks {
    val shadowJar: ShadowJar by getting
    shadowJar {
        // your config
    }
}
Or if you do not want to have
tasks {}
block:
val shadowJar: ShadowJar by tasks.getting {
    // your config
}
s

sdeleuze

05/28/2018, 11:56 AM
Thanks for your feedback. Could that make sense I suggest to the plugin author to add more configuration options to the extensions in order to have a useful
shadow { ... }
like in Groovy ?
I mean users just want to get something uesful by default, and
shadow { .. }
is what they are going to use.
Do you provide guidelines for Gradle plugin developers that make this kind of things clear ?
Any chance to have a feedback about what shadow plugin should do to improve compat with the Kotlin DSL (see my comments above) ?
g

gildor

05/31/2018, 11:21 AM
@sdeleuze what is your typical config for shadowJar?
Because problem that you mentioned is typical for many plugins, but shadow plugin has reasonable defaults.
As I understand recommendation for plugin authors is to have good defaults and configurable defaults for tasks, si shadow extension wouldbe probably useful
s

sdeleuze

05/31/2018, 12:39 PM
I would like to be able to do http://imperceptiblethoughts.com/shadow/#filtering_shadow_jar_contents by just writing
shadowJar { }
like in Groovy
Is there something Shadow Gradle plugin can do about that ?
Or do they have to copy these properties to the extension and get the tasks retrieve these properties ?
Is it by design that extension get short access via lambda but not tasks ?
g

gildor

05/31/2018, 1:52 PM
shadowJar on groovy is dynamic syntax you can do the same in Kotlin, but you don't have type safe context there, so it's mostly useless: tasks { "shadowJar" { this::class == Task::class } }
You should specify task type to have type safe accessors
For extensions Kotlin dsl generates type safe accessors, I remember that guys form Gradle mentioned that they probably will implement also for non-dynamic tasks to have type safe accessors for them too, but for now you should specify type manually using by getting or using reified generic syntax
Or, as alternative solution, ask plugin authors to use plugin extensions instead of direct task configuration, because most of use cases can be solved using rational defaults and extensions, without direct task configuration (if you enough default task and you don't want to create more using plugin default task as parent implementation)
Or do they have to copy these properties to the extension and get the tasks retrieve these properties ?
Yes, this is possible, you can use extensions config as default values for task config. As I remember the latest versions of Gradle even have some API to reduce boilerplate in this case
s

sdeleuze

05/31/2018, 2:37 PM
Ok thanks