Coersion of file for a task is pretty cool, yet the workaround is
fairly cheap. I think that the biggest gain from this story might
actually be kick starting a tidy-up in the convention mapping
business. So there you go, I think that that it's finally time to
start dealing with convention mappings :)
Backwards compatibility for convention mappings is pretty tricky. On
one hand, this feature was advertised as internal in past so
theoretically, we can change it. However, the change might affect
users that don't use the CMs at all, some users might just happen to
consume some 3rd party plugin that uses CMs. I guess that's true for
any kind of breaking change. Yet, I think that there's fair amount of
3rd party plugins that were inspired on Gradle codebase and hence use
CMs. I'd say that we should have generous migration plan for any
changes in CMs, ideally, we're just fully compatible :)
Cheers!
--
Szczepan Faber
Principal engineer@gradleware
Lead@mockito
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
