Just wanted to poke this issue since it has been over a year since a comment was left and this issue still exists. I have recently been struggling with getting my custom shadow task to include the dependencies in the thick jar until I changed my configuration to use
project.configurations.implementation.canBeResolved = true
configurations = project.configurations.implementation »
Prior to this build, my team used Gradle 6 and used the deprecated compile and runtime dependency declarations. We had also pointed our custom shadow task to use configurations = project.configurations.runtime » After upgrading to Gradle 7 and v7.1.2 of this plugin, we began running into issues with our jars missing dependencies.
Sign up for free
project.configurations.implementation.canBeResolved = true
configurations = project.configurations.implementation »
Prior to this build, my team used Gradle 6 and used the deprecated compile and runtime dependency declarations. We had also pointed our custom shadow task to use configurations = project.configurations.runtime » After upgrading to Gradle 7 and v7.1.2 of this plugin, we began running into issues with our jars missing dependencies.
Sign up for free
sourceSets.main.scala.srcDir "src/main/java"
sourceSets.main.java.srcDirs = »
sourceSets.test.scala.srcDir "src/test/java"
sourceSets.test.java.srcDirs = »
sourceSets.main.java.srcDirs = »
sourceSets.test.scala.srcDir "src/test/java"
sourceSets.test.java.srcDirs = »
Moreover, LAMBDA is the true lambda that we know and love: a lambda can be an argument to another lambda or its result; you can define the Church numerals; lambdas can return lambdas, so you can do currying; you can define a fixed-point combinator using LAMBDA and hence write recursive functions; and so on. (Additionally, since lambdas can be named, they can directly call themselves recursively, which is much more convenient than using a fixed-point combinator.)
