Please report issues like this in our bug database: http://dev.chromium.org/for-testers/bug-reporting-guidelines
On Thu, Sep 11, 2008 at 4:28 PM, Nick Fletcher <[EMAIL PROTECTED]> wrote: > > On Sep 11, 4:25 pm, Nick Fletcher <[EMAIL PROTECTED]> wrote: >> Hi, >> >> I've been developing a Java web service with Netbeans the past few >> days, and since I installed Chrome I have been experiencing build >> failures which I traced to a Windows file lock on the distribution >> directory. I installed the WhoLockMe utility (http://www.dr-hoiby.com/ >> WhoLockMe/) to find out which process was locking the directory. >> Surprise! It's Chrome. >> >> Now I have no idea why Chrome would be reading a directory that it >> should not even know exists, but there it is. >> >> Any ideas? >> >> Nick > > A thought just occurred to me that it's likely because I have been > deploying the WAR file using Chrome. It looks like Chrome is not > closing the directory when it's finished. > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
