Hi,
My old Grails plugin for Gradle creates a default rule like so:
// Convert any task executed from the command line into the
// Grails equivalent command.
project.tasks.addRule("Grails command") { String name ->
// Gradle has a tendency to want to create 'args' and 'env'
// tasks, so block it from doing so.
if (name == "args" || name == "env") return
// Add a task for the given Grails command.
project.task(name) << {
runGrailsWithProps(GrailsNameUtils.getNameFromScript(name), project)
}
}
The trouble is, if this plugin is applied to a build file and the user
then adds a custom task, say "myTask", then when that custom task is
called:
gradle myTask
Gradle complains that the task already exists. Should I change the way
that the plugin adds the rule?
Thanks,
Peter
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
