On 1 July 2014 at 9:07:02 am, Gary Hale (gary.h...@gradleware.com) wrote:
I think we need two things:
1. The name of the file that we fail to hash in that exception message
2. An exception that wraps exception that occur when snapshotting that
indicates the task, and the property of the task
> I think we need two things:
>
> 1. The name of the file that we fail to hash in that exception message
>
> 2. An exception that wraps exception that occur when snapshotting that
> indicates the task, and the property of the task that declares the files to
> be snapshotted
>
As far as #2 is concer
On 28 June 2014 at 1:55:24 am, Gary Hale (gary.h...@gradleware.com) wrote:
I've made a simple change to capture the file name in the exception when
hashing fails so this at least provides a minimum of information when this sort
of thing occurs, but it's pretty basic and doesn't really provide
I've made a simple change to capture the file name in the exception when
hashing fails so this at least provides a minimum of information when this
sort of thing occurs, but it's pretty basic and doesn't really provide
information about the context in which the error occurs.
I think part of the pr
Thanks Luke!
I'll point Dan and Andrés to this comment.
On Fri, Jun 27, 2014 at 1:50 AM, Luke Daley
wrote:
> Hi Guillaume,
>
> This basically boils down to a bug in the asciidoctor plugin and a terse
> error message on Gradle’s part. Please see Gary’s comment here:
> http://issues.gradle.org/br
Hi Guillaume,
This basically boils down to a bug in the asciidoctor plugin and a terse error
message on Gradle’s part. Please see Gary’s comment here:
http://issues.gradle.org/browse/GRADLE-2967?focusedCommentId=18916&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-
Thanks Luke!
On Fri, Jun 20, 2014 at 1:58 AM, Luke Daley
wrote:
> It’s too late to get this fixed in 2.0, but I’ll take a look when I’m back
> next week and see if we can get it fixed for 2.1.
>
> On 15 June 2014 at 10:29:01 pm, Guillaume Laforge (glafo...@gmail.com)
> wrote:
>
> Hi guys,
>
> T
It’s too late to get this fixed in 2.0, but I’ll take a look when I’m back next
week and see if we can get it fixed for 2.1.
On 15 June 2014 at 10:29:01 pm, Guillaume Laforge (glafo...@gmail.com) wrote:
Hi guys,
The Groovy project is affected by this Gradle issue here:
http://issues.gradle.org/