Thanks John.
--
Luke Daley
Principal Engineer
http://gradleware.com
On 10 Dec 2013, at 14:50, johnrengelman wrote:
Submitted pull request with design spec for changes:
https://github.com/gradle/gradle/pull/229
--
John Engelman
On Monday, December 9, 2013 at 3:34 PM, Luke Daley-2 [via Gradl
Sounds good.
Would you like me to submit the design spec to Gradle Core with that
same format?
If you're up for it, that would be a great way to make this happen.
--
John Engelman
On Monday, December 9, 2013 at 12:06 PM, Luke Daley-2 [via Gradle]
wrote:
Good stuff John,
I'll take a
Good stuff John,
I'll take a look at it and leave any applicable comments on GitHub.
One output of this work that I'd like to see is a design spec for the
work that needs to happen in the core to make this better supported.
Your plugin will be illuminating for that.
--
Luke Daley
Principal E
On 26 Nov 2013, at 15:00, johnrengelman wrote:
That sounds good Luke.
I'll submit a PR for core for the changes I need in the next couple of
days and then start up a plugin project.
Can you outline the core changes you need before hand? I'd like to
minimise this at this point.
--
John
On 22 Nov 2013, at 21:57, johnrengelman wrote:
This is my state at defining the API:
https://github.com/johnrengelman/gradle/commit/41c005e211c13237407db8ca031d8b215f9241c3
It does some work pulling apart the internal API for what makes sense
to expose through the public API. Most of it is
On 21 Nov 2013, at 16:34, johnrengelman wrote:
Could we add the functionality to the Project API through an extension
then?
Something like
project.extensions.async.javaFork { … } to get at it? Would that
help to separate it enough? I guess I write it as a separate plugin
entirely that adds
Hi all -
I've been finding more and more reasons in our build in our build to create
an implementation of java process forking. Currently the JavaExec
implementation is synchronous and I'm looking at implementing some features
that would allow a build to fork multiple processes and then blocking on
On 21 Nov 2013, at 3:11 pm, johnrengelman wrote:
> Hi all -
> I've been finding more and more reasons in our build in our build to create
> an implementation of java process forking. Currently the JavaExec
> implementation is synchronous and I'm looking at implementing some features
> that would
