On 15/07/2011, at 10:17 PM, Szczepan Faber wrote: > I would vote for figuring out a graceful way to move to extensions instead of > conventions. I.e. deprecate old behavior instead of breaking it. :) > If we were post 1.0 I'd be more inclined t agree, but given that we aren't and it's a very quick change for users to make, and is on the edges anyway, I'd prefer not carrying the extra baggage. > @Luke, can you elaborate on on your concern regarding dsl reference? >
We have a nice mechanism for describing what gets "mixed in" to core types, but this breaks down for extensions. Where do I document the “application” property that is added to Project? How do I get the docs for the actual extension into the DSL reference (besides using javadoc/groovydoc). The structure of this stuff is different to using convention mixins. I think we are going to have to do some work on the dsl docs generation to accommodate this change. I'm happy to do that, but it won't make m4. -- Luke Daley Principal Engineer, Gradleware http://gradleware.com
