On 17/01/2013, at 3:19 AM, Szczepan Faber wrote:

>> 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.

Build outcomes really represent actions, rather than things. For example, a 
build outcome can be an assertion like: running 'gradle build' produced build 
item 'jar'. It doesn't represent the build item 'jar' itself.

Another difference is that build outcomes are concerned only with the final 
result, not the intermediate steps. The build comparison doesn' care whether 
the byte code was compiled to a classes directory and then assembled into a 
jar, or just generated directly into a jar. It cares only that the jar produced 
by each build is the same.


> 
> 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?

We're not necessarily changing it, but we are adding some new types that also 
represents 'sets of source' but which have a different meaning to the existing 
thing called 'source set'. We can't just call all these different things 
'source set'. We can in a general sense, but we also need to have names for the 
specific concepts and types.


--
Adam Murdoch
Gradle Co-founder
http://www.gradle.org
VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting
http://www.gradleware.com

Reply via email to