2009/9/17 Adam Murdoch <[email protected]> > 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. > > Ok now I think I understand the reason for the language name in the name of the compile task. But I would have expected this to be incorporated in some sort of typing of source sets, so the name of the language is in the build script and doesn't have to be repeated on the command line.
This shows that there should be 2 different typings for source sets, what type of code it represents main code or test code, and in which language the code is written. and as mentioned also in an other thead have compileMain for the main source set but also have compile that compiles all the 'main' source sets. > 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 > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > >
