> Here's a potential approach to solving this problem: > The goal is that we want not just the 'wrapper' task to be implicitly > available, but also things like 'idea' and 'eclipse', and our future project > archetype equivalent. We don't really want to move all these things to core. > Instead, I think we want to have some way for the core to implicitly apply a > plugin when a particular task is mentioned on the command-line. So, when you > do 'gradle eclipse', and the eclipse plugin has not been applied to the > project, the core will implicitly apply it. Same for idea plugin. We could > potentially do the same for the wrapper. > More specifically: > * Add a wrapper plugin, which simply adds a Wrapper task instance. > * Change the ImplicitTasksConfigurer to apply the wrapper plugin to the > project. > Perhaps you could change your patch to take this approach?
Adam, Thanks for your suggestions - I felt that the refactoring solution was going against the grain, and am glad to hear you confirm it. I will research the ImplicitTasksConfigurer and the task rules better, and try to implement a solution along the lines of your suggestions. I need to research Gradle plugins more, but thanks to your e-mail I have a much clearer path for implementing this. I'll post an update next week. Thanks, --Nate > Once we've done that, we can change things to work better: > * Change the ImplicitTasksConfigurer so that it uses task rules, and remove > the idea of implicit tasks. We need to rework how rules work a bit, for this > to happen. > * Add rules for the idea and eclipse plugin. > * Maybe move the help tasks into a plugin and out of core. > And later: > * Maybe add some way for a plugin to register an implicit task rule with the > core. This way, the core wouldn't need to know about the plugins, but > instead could discover the implicit tasks. > * Maybe add some way for the core to use a repository to discover these > implicit task rules for external plugins. > > -- > Adam Murdoch > Gradle Co-founder > http://www.gradle.org > VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting > http://www.gradleware.com > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
