I think I mis-interpreted the "compare job history" output.
In any case, I've hacked together a working build ... I guess I just
needed to think about it over night. It doesn't use the Gradle task,
but instead hard-codes a couple of paths (to Gradle, primarily). Just
finished and its working!
O
On Fri, Apr 22, 2011 at 1:15 AM, Howard Lewis Ship wrote:
> Hm. Looks like user ngn reverted it to the old Maven based build.
> That isn't what we want or need!
Looking further into this, what made you think the build was reverted
into a Maven build? Your build output in your mail shows Gradle
ru
On Fri, Apr 22, 2011 at 1:15 AM, Howard Lewis Ship wrote:
> Hm. Looks like user ngn reverted it to the old Maven based build.
> That isn't what we want or need!
That would be me, but not what I intended to do. The only setting I
changed was to configure the installed Gradle to use. It was because
I've been trying to switch the Tapestry build over to Gradle (from Maven).
We had a hacky way of getting Maven running with the DISPLAY
environment variable set up, so that Xvfb & FireFox could be used as
part of the testing.
I attempted to reproduce that for the Gradle build, adding extra build
