So today, as I seem to have done way too many times, I typed "gradle
eclipse" and got back:
FAILURE: Could not determine which tasks to execute.
* What went wrong:
Task 'eclipse' not found in root project 'XYZ'.
The question that popped into my head is "why do I have to add 'apply
plugin: eclipse' to the build.gradle file just to run the eclipse
task? The eclipse plugin in built in so gradle knows about it. I just
typed "gradle eclipse", so gradle knows I want the eclipse plugin to
run. "What we've got here is a failure to communicate!" :)
So, I wonder if some or all of the built in plugins might be
"auto-applied" so that those tasks are available even if they are not
manually "applied". Of course external plugins need something to tell
gradle how to find them, and some plugins might require configuration
before they can function, but perhaps instead of a failure, gradle
could search the list of tasks in the built in plugins before giving
up? If it finds a match, apply the plugin then run the task.
Along those same lines, if I have a project that has .groovy files
inside src/main/groovy, shouldn't that be enough to tell gradle that
it should apply the groovy plugin? Similar for java and scala.
Requiring the "apply plugin" to be manually specified in the
build.gradle seems redundant.
Anyway, just a thought.
Philip
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
