xenoterracide
05/01/2018, 8:46 AMmp
05/02/2018, 12:20 PM-x foo
to not run task foo
gildor
05/03/2018, 10:15 AMwakingrufus
05/03/2018, 7:43 PMrun
commandcprigent
05/04/2018, 12:56 PMbuild.gradle
?xenoterracide
05/05/2018, 3:46 AMtest {
reports {
junitXml.enabled = false
html.enabled = true
}
}
in kotlin dslStefMa
05/05/2018, 6:08 PMxenoterracide
05/06/2018, 6:23 PMHAn
05/08/2018, 3:00 AMSrSouza
05/08/2018, 4:37 PMallprojects
or subprojects
block?xenoterracide
05/08/2018, 10:42 PMPlugin<Project>
is a generic, what asside from Project
can you use on a plugin?xenoterracide
05/08/2018, 11:33 PMval sourcesJar by tasks.creating(Jar::class) {
classifier = "sources"
from(java.sourceSets["main"].allSource)
}
trying to convert this code to java from kotlin for a plugin, but I'm not sure I understand the from
@Override
public void apply( Project project ) {
if ( System.getenv("JRS_S3_URI") != null ) {
project.getTasks().create( "sources", Jar.class, task -> {
List<SourceDirectorySet> collect
= getSourceSets().stream().map( SourceSet::getAllSource ).forEach( task::include );
task.include( collect );
} );
}
}
is the not compiling that I've come up with so farthatadamedwards
05/10/2018, 3:25 PMeskatos
05/11/2018, 12:03 PMval answer: String? by project
otakusenpai
05/11/2018, 2:48 PMjames_bassett
05/12/2018, 4:42 AMuseJunitPlatform()
, what am I meant to do if I call useJunitPlatform()
in a plugin (so every project gets the same Junit setup), but then want to customize the Junit config further (like adding extra tags) in my build.gradle.kts. I've found that when calling useJunitPlatform()
again in my build script, it clobbers the setup from my plugin (i.e. if I have any tags set, they get blown away by the new ones). I've had to get the options of my test task and cast to JunitPlatformOptions
and then call the functions (like includeTags()
) for it to work properly.Johan Vergeer
05/12/2018, 11:20 AMJohan Vergeer
05/12/2018, 4:50 PMnapperley
05/14/2018, 2:21 AMjames_bassett
05/14/2018, 8:04 AMsubprojects
block explicitly (i.e. even though i've applied the java plugin in my root build.gradle.kts with the plugin DSL, i have to apply it again in the subprojects block using apply { plugin("java") }
otherwise it doesn't let me define any common dependencies (as the testCompile configuration isn't available). So maybe you have to apply the maven-publish
plugin in your subprojects block for that extension to be visible.mkobit
05/15/2018, 3:17 PMsettings.gradle.kts
is red, but not my buildSrc/settings.gradle.kts
😕napperley
05/17/2018, 1:27 AMmax
05/17/2018, 6:21 PMsourceCompatibility
at the root of the buildscript, this property is not longer recognized in kts, what would be the equivalent dsl for setting it up? thanksbdawg.io
05/21/2018, 3:52 PM4.7-bin
and I have Use default gradle wrapper
selected, yet I keep getting errors in IntelliJ and the output logs are specifying Gradle 4.4 — running the same tasks with ./gradlew ...
on the command line yields a successful task with no errorsjlleitschuh
05/22/2018, 12:02 AMjakiej
05/22/2018, 10:17 PMgradle.ext
?Lex Luthra
05/23/2018, 7:22 AMjar {
manifest {
attributes 'Implementation-Title': project.name
}
}
gildor
05/23/2018, 7:29 AMtasks {
"jar"(Jar::class) {
manifest {
attributes 'Implementation-Title': project.name
}
}
}
Alowaniak
05/23/2018, 11:05 AMplugins{}
block is heavily recommended, isn't using apply<>()
and configure<>
also type-safe? The reason I'm sort of gravitating towards the apply
and configure
is because I feel like you can group it better together then (for e.g. make a `fun setupApplication() { /*appply and configure*/}`; but I'm very new to messing around with gradle and especially kotlin so maybe I'm misguided here?JoeHegarty
05/25/2018, 1:49 AM-Xenable-jvm-default
in Gradle?JoeHegarty
05/25/2018, 1:49 AM-Xenable-jvm-default
in Gradle?gildor
05/25/2018, 3:04 AMJoeHegarty
05/25/2018, 3:05 AM