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 = »
monotonically_increasing_id
df.withColumn("rank", rank().over(Window.partitionBy("Dept_id").orderBy($"salary".desc)))
.filter($"rank" <= 3)
.drop("rank")
.filter($"rank" <= 3)
.drop("rank")
