bart wrote: > > 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? >
You don't need to manipulate the workflow in order to achieve your goal. Just remove src/main/java from the set of Java source directories and add it to the set of Scala source directories, like Adam showed earlier. Then compileScala will compile both your Java and Scala code, and you can have bidirectional dependencies between Java and Scala without having to worry about what to compile first. The compileJava task will still be there but won't actually be doing anything. -- Peter Niederwieser Developer, Gradle http://www.gradle.org Trainer & Consultant, Gradleware http://www.gradleware.com Creator, Spock Framework http://spockframework.org -- View this message in context: http://gradle.1045684.n5.nabble.com/Mixed-Scala-Java-project-tp3378120p4374932.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
