> 1. A term for the things that Gradle builds. With this work, plus
> publications, components, reports and distributions work that is happening,
> we're starting to model more of the things that Gradle can build. It feels
> like we should have a term for this. So far we've been calling these things
> 'things' and sometimes 'outputs'. I kind of like the term 'build item' from
> abuild.
In the tooling api we've started calling those things 'build
outcomes'. Though, not sure how much they fit.
I don't love 'build item' because to me it does not say that it's a
product of build (e.g. in my head it links with a thing to be built).
I don't have anything better so if 'build item' works for everyone
then it works.
> 4. A term for a logical set of source. Currently we call these a 'source
> set'. The spec calls these things a 'functional source set'.
Current name does not bother me (but maybe I simply got used to it :)
- why do we want to change it?
Cheers!
--
Szczepan Faber
Principal engineer@gradleware
Lead@mockito
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
