2009/4/22 Adam Murdoch <[email protected]> > > > Tom Eyckmans wrote: > >> I was thinking about doing something to make the blocks that we provide in >> the build file (repositories, configurations, dependencies) more >> general/flexible. This is probably not as related to what you were bringing >> up Adam but it just came to my mind when reading ConfigurationContainer :)) >> . Currently this is something that seems to static to me. Wouldn't it be >> cool if plugins would be able to add blocks? >> >> > They already can. They just add a convention object with 2 methods: > > ThingContainer getThings(); > void things(Closure);
True, this exactly what we do on project. > > If it makes sense, the ThingContainer implementation can extend > DefaultDomainObjectContainer<Thing> to pick up all the > get/find/configure/iterate methods that the other containers have. Or not. > > Perhaps I'm missing the problem? I just think it would be nice to have this block concept in place in some way that it is easy to factor out of project or a plugin convention object. I agree that is something minor but this is something that will be repeated multiple times by different plugins or on project as we add things. Also I don't think a block is something that should be in/belong to a convention object. > > > Adam > > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > >
