On Wed, Jan 16, 2013 at 9:37 PM, Adam Murdoch
wrote:
>
> On 17/01/2013, at 3:45 AM, Luke Daley wrote:
>
>
>
> On 16/01/2013, at 6:06, Adam Murdoch wrote:
>
> Hi,
>
> To better support building Android apps (and other things), we want to
> rework the jvm language plugins so that they can handle bu
On 17/01/2013, at 5:01 PM, Daz DeBoer wrote:
>
>
> On 15 January 2013 23:06, Adam Murdoch 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
On 15 January 2013 23:06, Adam Murdoch 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
Another question is how to group source sets and packagings.
For source sets, we currently use two approaches:
- For Java, Scala, Groovy, ANTRL and resources, we use the functional source
sets, adding the source to `sourceSets.${function}.${language}`.
- For C++, we use language specific source
G'day
Gradle-1.4-rc-1 is out! Read the full announcement at
http://forums.gradle.org/gradle/topics/gradle_1_4_rc_1_available_for_testing
.
Please take the time to try it out and let us know if you encounter any
issues.
cheers
--
Darrell (Daz) DeBoer
Principal Engineer, Gradleware
http://www.gra
On 17/01/2013, at 6:47 AM, Marcin Erdmann wrote:
> On 01/16/2013 07:30 PM, Adam Murdoch wrote:
>>> Do you think that what I currently have is worth of a pull request and
>>> merging it in?
>>
>> Absolutely.
>
> So there it is: https://github.com/gradle/gradle/pull/121
Awesome. Thanks for this
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
On 17/01/2013, at 3:45 AM, Luke Daley wrote:
>
>
> On 16/01/2013, at 6:06, Adam Murdoch 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 s
Adam Murdoch wrote
> Currently, a test framework needs to provide the following pieces:
>
> 1. A set of framework-specific options to expose to the DSL.
> 2. A test detector implementation that takes these options and the test
> classpath, and builds a sequence of test execution requests.
> 3. A t
On 01/16/2013 07:30 PM, Adam Murdoch wrote:
Do you think that what I currently have is worth of a pull request
and merging it in?
Absolutely.
So there it is: https://github.com/gradle/gradle/pull/121
-
To unsubscribe from th
On 17/01/2013, at 1:00 AM, Luke Daley wrote:
>
> On 16/01/2013, at 1:47 PM, Hans Dockter wrote:
>
>>
>>
>> On Wed, Jan 16, 2013 at 2:43 PM, Luke Daley
>> wrote:
>>
>> On 16/01/2013, at 1:25 PM, Hans Dockter wrote:
>>
>>>
>>>
>>> On Wed, Jan 16, 2013 at 2:08 PM, Luke Daley
>>> wrote:
On 17/01/2013, at 12:39 AM, Marcin Erdmann wrote:
>
>
> On Wed, Jan 16, 2013 at 7:05 AM, Adam Murdoch
> wrote:
>
> On 16/01/2013, at 9:50 AM, Marcin Erdmann wrote:
>
>> The next iteration of my effort on build dasboard plugin is available at:
>> https://github.com/erdi/gradle/tree/reportin
On 16/01/2013, at 6:06, Adam Murdoch 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,
On 16/01/2013, at 4:19 PM, 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 hav
> 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 thing
I would love to see this improved soon. Thanks a lot Luke for bringing
this up. Until 2.0 we might be deprecating more and more stuff and
this an excellent (and relatively cheap) opportunity to earn some
happiness points with our users.
Cheers!
On Wed, Jan 16, 2013 at 3:00 PM, Luke Daley wrote:
On 16/01/2013, at 1:47 PM, Hans Dockter wrote:
>
>
> On Wed, Jan 16, 2013 at 2:43 PM, Luke Daley wrote:
>
> On 16/01/2013, at 1:25 PM, Hans Dockter wrote:
>
> >
> >
> > On Wed, Jan 16, 2013 at 2:08 PM, Luke Daley
> > wrote:
> > There was talk around the 1.2 era where we were talking abou
On Wed, Jan 16, 2013 at 2:43 PM, Luke Daley wrote:
>
> On 16/01/2013, at 1:25 PM, Hans Dockter
> wrote:
>
> >
> >
> > On Wed, Jan 16, 2013 at 2:08 PM, Luke Daley
> wrote:
> > There was talk around the 1.2 era where we were talking about improving
> the user experience when dealing with deprecati
On Wed, Jan 16, 2013 at 2:39 PM, Marcin Erdmann
wrote:
>
>
> On Wed, Jan 16, 2013 at 7:05 AM, Adam Murdoch > wrote:
>
>>
>> On 16/01/2013, at 9:50 AM, Marcin Erdmann wrote:
>>
>> The next iteration of my effort on build dasboard plugin is available at:
>> https://github.com/erdi/gradle/tree/repor
On 16/01/2013, at 1:25 PM, Hans Dockter wrote:
>
>
> On Wed, Jan 16, 2013 at 2:08 PM, Luke Daley wrote:
> There was talk around the 1.2 era where we were talking about improving the
> user experience when dealing with deprecations. I think we should bump up the
> priority of this and addres
On Wed, Jan 16, 2013 at 7:05 AM, Adam Murdoch
wrote:
>
> On 16/01/2013, at 9:50 AM, Marcin Erdmann wrote:
>
> The next iteration of my effort on build dasboard plugin is available at:
> https://github.com/erdi/gradle/tree/reporting-improvements.
>
> Following is what has been done since my last em
On Wed, Jan 16, 2013 at 2:08 PM, Luke Daley wrote:
> There was talk around the 1.2 era where we were talking about improving
> the user experience when dealing with deprecations. I think we should bump
> up the priority of this and address it in the next release or two.
>
> I just updated an old p
There was talk around the 1.2 era where we were talking about improving the
user experience when dealing with deprecations. I think we should bump up the
priority of this and address it in the next release or two.
I just updated an old project to 1.3 and received: “The
Project.dependsOnChildren
23 matches
Mail list logo
