This message was deleted.
# community-supports
Slackbot
08/16/2023, 9:14 AMThis message was deleted.
v
Vampire
08/16/2023, 9:49 AMHow does your settings script look like?
Vampire
08/16/2023, 9:49 AMCan you share a build
--scanl
Lu Cao
08/17/2023, 6:44 AMThanks for the quick response! I found that after I removed the
rootProject.nameLu Cao
08/17/2023, 12:56 PMHi Vampire,
I want to confirm another question. It looks like gradle cannot support java-scala mixed project very well. Because in gradle compile DAG, the compileScala task depends on compileJava task, while in real projects, my java class could depens on the scala class in the same module. That will be a circle in compile path. Now my solution is moving all the java class files from
src/main/javasrc/main/scala/v
Vampire
08/17/2023, 1:07 PMIf you have a clear direction, so either Java code uses Scala code or Scala code uses Java code, you can define the order / dependency.
But if you really have a big mixture with both, and the Scala compiler can do the joint compilation, it is probably fine to let it do it. But I have no experience at all with Scala.
Alternatively to moving the Java files to the Scala source set, you could maybe just define the Java source directory for the Scala source set and change the Java source directory so that the Java compilation task has nothing to do.
l
Lu Cao
08/18/2023, 2:26 AMAh……yes I saw the proposal and also tried to change java source set. But that will cause another error, something like ‘java source set cannot be empty’, because some other modules could depends on the current javaCompile task
v
Vampire
08/18/2023, 7:54 AMIf it complains that the source set must not be empty, you should have the same problem when moving all source files over though