Adam Murdoch wrote:
Hi,
I've been making some changes to allow any combination of Java, Groovy
and Scala source to be used for a project. The guts of this change is
that the 'compile' task of each source set has been split into:
- compileJava: of type Compile, compiles every thing in src/main/java
using javac
- compileGroovy: of type GroovyCompile, compiles everything in
src/main/groovy using groovyc+javac. Handles joint groovy and java
compilation
- compileScala: of type ScalaCompile, compiles everything in
src/main/scala using scalac+javac. Handles joint scala and java compilation
- compile: dependsOn compileJava, compileGroovy, compileScala,
processResources
compileGroovy and compileScala are added by the Groovy and Scala
plugins, respectively. The rest are added by the Java plugin.
We don't handle joint Groovy, Scala and Java compilation.
I've also made some changes to the lifecycle tasks:
- libs and dists have been merged into assemble
- moved the check task from the code quality plugin to the java plugin
- changed check to depend on test
Adam
I don't have a better answer, but I still feel it is awkward to have the
language in the task name. Even if I could always use the compile task from the
command line (because of the dependency), I have to use the task with the
language name when setting up the options. I guess it's just habit, but I keep
using compile.options.
--
Steve Appling
Automated Logic Research Team
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
