Re: [gradle-dev] Naming scheme for component model

2014-07-22 Thread Adam Murdoch
On 22 Jul 2014, at 12:35 pm, Andrew Oberstar wrote: > Would something like minified JavaScript be in scope here? > Yes, absolutely. It should cover any kind of software artefact, including those that happen to be encoded as text instead of some binary format, such as libraries or apps made up

Re: [gradle-dev] Naming scheme for component model

2014-07-21 Thread Andrew Oberstar
Would something like minified JavaScript be in scope here? If so, binary may be too limiting Andrew Oberstar On Jul 21, 2014 8:54 PM, "Adam Murdoch" wrote: > > On 19 Jul 2014, at 2:52 am, Daz DeBoer > wrote: > > G'day > > The new 'native runtime' support (C/C++/etc) introduced a powerful > comp

Re: [gradle-dev] Naming scheme for component model

2014-07-21 Thread Adam Murdoch
On 19 Jul 2014, at 2:52 am, Daz DeBoer wrote: > G'day > > The new 'native runtime' support (C/C++/etc) introduced a powerful component > model for defining the software you are trying to build: libraries, > applications, variants, buildTypes, etc. We're now rolling this concept into > the jv

[gradle-dev] Naming scheme for component model

2014-07-18 Thread Daz DeBoer
G'day The new 'native runtime' support (C/C++/etc) introduced a powerful component model for defining the software you are trying to build: libraries, applications, variants, buildTypes, etc. We're now rolling this concept into the jvm runtime, with a new set of 'component' plugins that will give