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
g

gotoOla

01/14/2019, 8:09 AM
Does anyone know how you could go about keeping the run task without using the application plugin and still having the hot reload? The reason why I want to get rid of the application plugin is because it has a lot of the distribution tasks and we are packaging it with the shadow plugin
n

Nikky

01/14/2019, 11:35 PM
so why get rid of it ? using application plugin and shadowJar together works fine and sets up the manifest for you.. whats so bad about that ?
i am not sure there is a
JavaExec
task available without the application plugin and you will have to deal with setting up the arguments and possibly classpath as well.. depending on the complexity of your project
g

gildor

01/15/2019, 12:59 AM
Shadow jar has great support of application plugin and provide shadow versions of all application plugin tasks, so I see no reason to get rid of application plugin
d

DALDEI

01/15/2019, 6:42 AM
Curious (for own use) which shadow jar plugin are you using ?
g

gotoOla

01/15/2019, 2:21 PM
The reason why I want to get away from the application plugin is because it comes with a lot of unecessary tasks for our use case (especially the distribution plugin which is transitive). So if the only thing that we are using from the application plugin is the run task it felt a bit like bringing in a tank to deliver a small package 😛
@DALDEI I have been using both version 2.x.x of the shadow plugin (I think this is the one in the ktor documentation) and 4.x.x and I haven’t experienced any problems with either of them
but I think I got it to work with
task run(type: JavaExec) {
    classpath = sourceSets.main.runtimeClasspath
    main = mainClassName
}
g

gildor

01/15/2019, 2:40 PM
Shadow also uses application plugin, so you cannot get rid of it without reimplementing everything yourself. I still don't see any reason. If those tasks are really bothering you, you can disable them and use only shadow versions
Also application plugin already bundled with Gradle and uses lazy task resolution, so you pay nothing for application plugin
g

gotoOla

01/15/2019, 4:33 PM
@gildor ah cool I didn’t know that. So just bringing in the shadow-plugin will give you the distTar and distZip tasks? Then I agree, it sounds more and more like there’s no real use case for it
Would be interesting to know how that works because if I run (without the application plugin)
./gradlew build -m
:discoverMainScriptsExtensions SKIPPED
:compileKotlin SKIPPED
:compileJava SKIPPED
:processResources SKIPPED
:classes SKIPPED
:inspectClassesForKotlinIC SKIPPED
:jar SKIPPED
:assemble SKIPPED
:discoverTestScriptsExtensions SKIPPED
:compileTestKotlin SKIPPED
:compileTestJava SKIPPED
:processTestResources SKIPPED
:testClasses SKIPPED
:test SKIPPED
:check SKIPPED
:shadowJar SKIPPED
:build SKIPPED
whilest with the application plugin I see shadowDistZip and all of the distribution tasks (distZip, distTar etc)
(but with these plugins/plugin setup)
apply plugin: 'com.github.johnrengelman.shadow'
apply plugin: 'java'
apply plugin: 'kotlin'

tasks.build.dependsOn tasks.shadowJar
g

gildor

01/15/2019, 4:39 PM
Because this config builds and jar and shadowJar, which probably not what you want
g

gotoOla

01/15/2019, 4:42 PM
So what I try right now is that I do this and then I have a dockerfile which pretty much does
ADD ./build/libs/app.jar app.jar
or would I miss out on anything from the application plugin by doing this?
(I should probably also say that this does not get published as any kind of maven artifact. The end result is a versioned docker image)
g

gildor

01/15/2019, 4:48 PM
Application plugin just allows to create jar file with correct meta to make jar executable
You apply application plugin and shadow plugin, then build shadow jar which will contain all the dependencies and correct meta-inf so jar will be executable
Task
build
already depends on
jar
task, if you don't need common (non fat) jar, just disable this task
Or just run shadowJar and only shadow jar will be created (by default it has name with version and classifier
all
, but this is configurable)
Such jar (with all dependencies and application plugin) can be executed like this:
java -jar your-app.jar
Without application plugin it will not work
g

gotoOla

01/15/2019, 5:18 PM
What do you mean by that it will not work at all? Not starting at all or will the manifest file be wrong?
apply plugin: 'com.github.johnrengelman.shadow'
apply plugin: 'java'
apply plugin: 'kotlin'

tasks.build.dependsOn tasks.shadowJar
def appName="app"
mainClassName="my.example.AppKt"

shadowJar {
    baseName = appName
    classifier = null
    version = null
    manifest {
        attributes 'Main-Class': mainClassName
    }
}
becuase with this I am able to do
java -jar
on the produced “app.jar”
(just trying to undertstand btw, I realise it might be a bit frustrating with all of these stupid questions)