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 that declares the files to be snapshotted As far as #2 is concerned, getting the property of the task that declares the input might be pretty involved. Problem is, once the inputs are added, they just get aggregated together and there is no post facto way to map resolved file to input property. I think I see a way to achieve that, but it would require more than a little refactoring of the inputs/outputs handling. I guess I'm wondering whether the effort/value balance is there for this specific case. Maybe the right question is whether having a full lifecycle mapping of input file to input property (and vice versa) would be valuable in other scenarios? Given this, let’s drop identifying the property. Just knowing which task and that it was determining up to date status would still be helpful. Gary 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-18916. On 20 June 2014 at 5:52:25 pm, Guillaume Laforge (glafo...@gmail.com) wrote: Thanks Luke! On Fri, Jun 20, 2014 at 1:58 AM, Luke Daley <luke.da...@gradleware.com> 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, The Groovy project is affected by this Gradle issue here: http://issues.gradle.org/browse/GRADLE-2967 It affects users only on Windows (a file locking issue), with the Asciidoctor plugin, but as well with other plugins as users reported. For us (Groovy project), it prevents building the documentation of Groovy on a Windows machine. I'd be happy to see our Gradle experts investigate that issue, and find a workaround for this Windows specific problem. Thanks for your attention. -- Guillaume Laforge Groovy Project Manager Pivotal, Inc. Blog: http://glaforge.appspot.com/ Social: @glaforge / Google+ — Luke Daley Gradleware Join us for Gradle Summit 2014, June 12th and 13th in Santa Clara, CA: http://www.gradlesummit.com -- Guillaume Laforge Groovy Project Manager Pivotal, Inc. Blog: http://glaforge.appspot.com/ Social: @glaforge / Google+ — Luke Daley Gradleware — Luke Daley http://www.gradleware.com — Luke Daley http://www.gradleware.com
