Steve Appling wrote:
I have not been paying enough attention to the source set changes, but
one item caught my eye today that I really would like to see changed.
I fully support the concept of source sets where you have groups of
source divided by function: main, test, integTest, etc. This is great!
I don't, however, like the inclusion of the language as part of the
task name. I don't think that the user should have to know whether to
call compileGroovy or compile or compileScala. I have been bit
several times now by calling project:compile and nothing happens.
There is a compile task, it just does nothing. I didn't know to call
project:compileGroovy.
I'm curious why you're calling the compile task from the command-line?
Not that what you point out above isn't a problem, I think it is. If we
know what your use case is, we can come up with a solution.
Before we release 0.8, I think it would be good to use source sets in
gradle's own project for integration Tests. I think our own
build.gradle is often used as an example for others. It is actually a
little sad how complicated it is now.
Indeed. There's a few things we've discussed recently which will clean
it up, but I think they're post-0.8 things:
- A java application plugin
- An aggregating project plugin
- Moving documentation + samples into their own subproject
- Task dependency auto-wiring
Adam
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
