Javier
03/25/2020, 3:10 PMorg.gradle.kotlin.dsl
but I can't find it.Gunslingor
03/26/2020, 12:13 AMmbonnin
03/26/2020, 4:48 PM./gradlew buildEnvironment
?turansky
03/27/2020, 11:35 AMkotllin-dsl
version compatible with kotlin plugin 1.4-M1
?cpe
03/27/2020, 11:53 AMtasks.register("bootRunDev") {
System.setProperty("spring.profiles.active", "dev")
finalizedBy(tasks.bootRun)
}
However, this is not working - the property is not recognized. I also tried to extend the BootRun
Profile:
task<BootRun>("bootRunDev") {
systemProperties["spring.profiles.active"] = "dev"
dependsOn("bootRun")
}
Both approaches don’t work.
Is there a way to do it?bjonnh
03/27/2020, 4:29 PMbjonnh
03/27/2020, 4:29 PMsanogueralorenzo
03/29/2020, 2:16 AM.kts
?
task all(type: GradleBuild) { tasks = ["independentTask1", "independentTask2"] }
Stephan Schroeder
03/29/2020, 10:59 AMinternal
modifier to mutually hide classes inbetween main and main2. So this is the expected folder structure:
src/main/kotlin
src/main2/kotlin
src/test/kotlin
I've come pretty far by add this to my build.gradle.kts
sourceSets {
val mainSourceSet: SourceSet = sourceSets["main"]
val testSourceSet: SourceSet = sourceSets["test"]
val main2SourceSet: SourceSet = create("main2") {
compileClasspath += mainSourceSet.output
runtimeClasspath += mainSourceSet.output
}
mainSourceSet.compileClasspath += main2SourceSet.output
mainSourceSet.runtimeClasspath += main2SourceSet.output
testSourceSet.compileClasspath += main2SourceSet.output
testSourceSet.runtimeClasspath += main2SourceSet.output
}
now
• code in main can see all the public classes from main2 but not the internal ones
• code in main2 can see all the public classes from main but not the internal ones
• code in test can see all the public and internal classes from main
• code in test can only see the public classes from main2
How do I make the internal classes from main2 accessible to test?Ahmed Ibrahim
04/02/2020, 11:28 AMbuildSrc
instead?
implementation(group = "", name = "facebook-login-6.3.0-jetified", ext = "aar")
In buildSrc I can't access the implementation
function, and I can only do add("implementation", "put-the-local-aar-here")
, the question is how can I include the local aar through the add function which is only available under only the buildSrc
?LastExceed
04/04/2020, 9:33 AMpublishing {}
block which isn't even possible (workaround here: https://stackoverflow.com/questions/54654376/why-is-publishing-function-not-being-found-in-my-custom-gradle-kts-file-within ) and doesn't give me any information on how to configure it for a kotlin project.
can someone help me? maybe someone has a working project setup that i can look at ? I am completely lostDariusz Kuc
04/04/2020, 8:58 PMmaven-publish
pom.xml
and the one that is generated by java-gradle-plugin
?, e.g. I got multi module project where I create pom.xml
for all subprojects so it includes same license info, etc (https://github.com/dariuszkuc/graphql-kotlin/blob/plugin/build.gradle.kts#L132). It looks like java-gradle-plugin
creates its own (very limited one) and ignores the generated pom (https://github.com/dariuszkuc/graphql-kotlin/blob/plugin/plugins/graphql-kotlin-gradle-plugin/build.gradle.kts#L11). Any suggestions? Thanks!JP
04/08/2020, 12:04 PMbuild.gradle.kts
after the prior build, like
dependencies {
// ...
implementation("org.springframework.boot:spring-boot-starter-security")
implementation("org.springframework.security:spring-security-test")
}
, but when I build in IntelliJ, the new dependencies doesn’t get installed: I can’t see them in the External Libraries, and I can’t import them. Am I missing something here? Or is there a certain other way to update the dependencies?Holger Steinhauer [Mod]
04/08/2020, 4:34 PMtasks {
val waitServer by creating {
group = "Docker"
description = "Spin-up fresh builds via Docker"
dependsOn (":reconciliation:dockerBuildImage")
dependsOn(composeUp)
}
}
So I would expect that ./gradlew waitServer
would call dockerBuildImage
on the reconciliation
module first and then run composeUp
. But it goes straight into composeUp
which fails because the docker image from the reconciliation
module isn’t built yet. Any ideas?rolgalan
04/09/2020, 3:42 PMbuildSrc/build.gradle.kts
file and the rest of buildSrc files?
I have some configuration that I use in some of my plugins that I also would like to reuse in the build.gradle file. However, this file is used to build the buildSrc, so I cannot reference to any of my buildSrc helper classes.
I don’t know if I’m missing something or this just is not achievable. Any help?Dariusz Kuc
04/09/2020, 8:06 PMA
and B
) that can be executed independently of each other
• task B
can optionally take an input from task A
output (or just read file from a file system)
• [works] I would like to provide an option for end users to either configure tasks directly in their build scripts
// build.gradle.kts
val a by tasks.getting(TaskA::class) {
propA.set("whatever")
}
tasks.withType(TaskB::class) {
propB.set("xyz")
input.set(a.output)
dependsOn("taskA")
}
• [doesn't work] I would also like to provide an option to to automatically create those tasks and their dependencies if project extension is configured, e.g.
// build.gradle.kts
myExtension {
propA = "whatever"
propB = "xyz"
}
Is that even possible?Joffrey
04/12/2020, 5:01 PMursus
04/15/2020, 9:58 PMimplementation
anyways?bjonnh
04/17/2020, 2:53 PMEyeCon
04/19/2020, 12:54 PMgradle init
. It seems to work — it downloads dependencies, builds etc. Now I'm trying to navigate around in the source and it doesn't seem to work with this project. It used to run previously (in other projects), but this is the first time I'm starting a project with Gradle. I just updated IntelliJ too, I hope this isn't some very recent bug. Basically I can't navigate to Gradle-downloaded definitions. Anyone have any ideas? I did invalidate the cache and restart.Javier
04/19/2020, 3:08 PMmaven-publish
plugin but for some reason, there are multiple versions uploaded.John Peña
04/20/2020, 10:45 PMDiagnosticControllerTest
doesn't have 151 linesJohn Peña
04/21/2020, 5:25 PMjuro
04/21/2020, 5:48 PMdependencies { constraints { api("${Libs.LIBRARY}:${version}@aar") } }
and using implementation(Libs.LIBRARY)
in my :app gradle this dependency fails to resolve
im sure there is some parameter which could be used to define extensions, but i cant seem to figure out how to do itPeter
04/22/2020, 7:10 PMval
but they don’t appear to be in scope for the buildscript
block right below, though work fine for allscripts
or subprojects
eg:
val artifactVersion: String by project
buildscript {
version = artifactVersion // unresolved reference
}
allprojects {
version = artifactVersion // ok
}
seeing as these constants are dependent on project
it’s not clear how I can move this to buildSrc
and make them available everywhere.
if i redeclare them with the buildscript
block it works but that defeats the purpose (i have many of these constants)kevin.cianfarini
04/22/2020, 8:27 PMrepositories {
jcenter()
maven { url = uri("<https://dl.bintray.com/mipt-npm/dev>") }
}
kotlin {
jvm()
linuxX64("linux")
sourceSets {
val commonMain by getting {
dependencies {
implementation(kotlin("stdlib-common"))
implementation("org.jetbrains.kotlinx:kotlinx-io:0.2.0-npm-dev-7")
}
}
Dustyn
04/24/2020, 3:24 PMjavafx.graphics does not "opens javafx.scene" to unnamed modul
. Does anybody spot the problem? https://gist.github.com/deggers/804cb1ffe6853d968ab58683e0f3318fx80486
04/24/2020, 6:20 PMsrc
, etc. ...so I'm not expecting that Gradle executes anything on it, but on the modules within that umbrella project...any clues? In Maven that's correctly executed, so I think there should be an equivalent in Gradle...thanks in advance!bod
04/25/2020, 1:22 PMkts
. Let's say I want some globally accessible map for dependency versions (for instance "gradle" to "6.3", "kotlin" to "1.3.70"
and so on) - and I'd like to be able to access it from the root's build.gradle.kts, and also the other module's. What's the simplest way to do this? Currently I have a solution using extra
but is there a way to simply add my own object
to the classpath or something like that?Javier
04/27/2020, 9:43 PMsigning.gnupg.passphrase
as gradle publish
task param instead of defining it in gradle.properties?