I, for one, like to keep my Groovy and Java stuff fairly separate. I use Groovy for a different level of my application than where I use Java (or Scala), and so it is nice that the default allows for the distinction.
~~ Robert. On Tue, Nov 22, 2011 at 2:32 AM, Peter Niederwieser <pnied...@gmail.com> wrote: > > David Kowis wrote >> >> Yeah, I ended up setting the CompileJava task to skip, and added the >> src/main/java to the groovy srcDir. >> >> Is this the ideal convention? >> >> Why not have the groovy plug in do this by default? >> > > I'm not sure which is the ideal convention, but the current convention is > more flexible in that you can control which Java files are joint-compiled > and which are passed directly to javac. > > -- > Peter Niederwieser > Principal Engineer, Gradleware > http://gradleware.com > Creator, Spock Framework > http://spockframework.org > Twitter: @pniederw > > > -- > View this message in context: > http://gradle.1045684.n5.nabble.com/Problem-building-groovy-test-code-tp5012007p5012731.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 > > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email