On Wed, Jan 16, 2013 at 9:37 PM, Adam Murdoch <[email protected]>wrote:
> > On 17/01/2013, at 3:45 AM, Luke Daley wrote: > > > > On 16/01/2013, at 6:06, Adam Murdoch <[email protected]> wrote: > > Hi, > > To better support building Android apps (and other things), we want to > rework the jvm language plugins so that they can handle building multiple > outputs from a given set of source files. > > I've made a bit of a start on a spec here, but's pretty rough: > https://github.com/gradle/gradle/blob/master/design-docs/building-multiple-outputs-from-jvm-languages.md > > I need some suggestions for terminology: > > 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. > > > I don't fully understand the scope of what this thing is. > > Is it anything that can be produced during a build? Or is it something > that is produced as a kind of primary goal? > > > The scope is pretty broad: Pretty much any thing that can be used during a > build. This includes the things that are produced as a primary output and > the things that are intermediate. It also include the things consumed by a > build. > Just to be sure. You definition is: set of build items = build inputs + built outputs ? Hans
