On 7 Mar 2014, at 10:17 am, Luke Daley wrote:
>
>
> On 24 February 2014 at 6:14:40 pm, Adam Murdoch (adam.murd...@gradleware.com)
> wrote:
>
>> Hi,
>>
>> I’m looking for some suggestions for names for some concepts we’re trying to
>> model in the tooling API (and elsewhere).
>>
>> On the
On Fri, Mar 7, 2014 at 12:17 AM, Luke Daley wrote:
>
>
> On 24 February 2014 at 6:14:40 pm, Adam Murdoch (
> adam.murd...@gradleware.com) wrote:
>
> Hi,
>
> I'm looking for some suggestions for names for some concepts we're trying
> to model in the tooling API (and elsewhere).
>
> On the command-l
On 24 February 2014 at 6:14:40 pm, Adam Murdoch (adam.murd...@gradleware.com)
wrote:
Hi,
I’m looking for some suggestions for names for some concepts we’re trying to
model in the tooling API (and elsewhere).
On the command-line, you can specify a bunch of things that you want Gradle to
do.
To be honest, I always liked the 'TaskSelector' that is-a 'EntryPoint'.
Until I read your email and started thinking about it :)
Some suggestions:
TaskName
TaskPath
RequestedTask
RequestedAction
RequestedOperation
BuildAction
BuildOperation
BuildItem
GradleAction
If the current names stay as th
Hi,
I’m looking for some suggestions for names for some concepts we’re trying to
model in the tooling API (and elsewhere).
On the command-line, you can specify a bunch of things that you want Gradle to
do. There are 3 kinds of things you can provide:
1. A qualified path, which means ‘run the t
