I'm running into this same issue. While I understand that one solution is to place any java classes that depend on scala in the scala source directory, that seems "wrong" to me since they are java files, not scala files. If you are going to combine scala and java classes anyway, why even have the initial separation?
In ANT I solved this by keeping the java and scala classes in their own directories and compiling scala first with both java/scala classes and then compiling java adding the "classes" directory to the javac classpath. In gradle when I execute "compileScala" the scala plugin enforces a convention that calls compileJava first and then compileScala. This is the exact opposite of what I want it to do. If the plugin didn't call compileJava first I could simply add the java source directory to the scala sourceSet and all would be fine. Does anyone know how to manipulate the workflow so the compileJava is not implicitly called by compileScala? Thanks, Bart -- View this message in context: http://gradle.1045684.n5.nabble.com/Mixed-Scala-Java-project-tp3378120p4373371.html Sent from the gradle-user mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
