Are you able to create a fork of the gradle repo on github and push your changes to that?
It's much easier to review changes that way as we can look at them in context. On 18/07/2011, at 8:52 AM, Merlyn Albery-Speyer wrote: > Adam/Luke, > > Ok, so have a local changeset that works for option 1: > > On Sat, Jul 2, 2011 at 12:53 AM, Adam Murdoch > <[email protected]> wrote: >> 1. apply group: 'mygroup', name: 'myplugin-project', version: '1.0', plugin: >> 'myplugin' > > I had difficulty getting a handle to a DependencyFactory (it's not in > the Project's ServiceRegistry), so what I have right now is adding > configuration to the ScriptHandler's ConfigurationContainer, and then > using the ScriptHandler's DependencyHandler to add the dependency: > > private Configuration createConfigurationWithDependency(Project > project, String group, String name, String version) { > ConfigurationContainer configurationContainer = > project.getBuildscript().getConfigurations(); > String configurationName = "plugin_"+group+"_"+name+"_"+version; > Configuration configuration = > configurationContainer.findByName(configurationName); > if (configuration == null) { > configuration = configurationContainer.add(configurationName); > project.getBuildscript().getDependencies().add(configurationName, > group + ":" + name + ":" + version); > } > return configuration; > } > > Any suggestions for improving on this? > > Cheers, > Merlyn > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > -- Luke Daley Principal Engineer, Gradleware http://gradleware.com --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
