Not sure JB to be honest, my global gitignore can have hidden them cause it starts with a dot. Was more to share it case it is encountered than to ask for a fix since I'm not sure ATM it comes from beam itself - also wonder if it can happen on the CI if both builds are executed.
Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github | LinkedIn 2017-11-24 10:02 GMT+01:00 Jean-Baptiste Onofré <[email protected]>: > Hi Romain, > > I guess they are not part of the repo (git clean -x -f -d removes it), > correct ? > > Let me try. > > Thanks, > Regards > JB > > > On 11/24/2017 10:00 AM, Romain Manni-Bucau wrote: >> >> Hi guys, >> >> I don't really know if it comes from my gradle tests or the gradle >> build itself but I realize this morning I had ".gogradle" files in >> beam in a few places and when building with maven the resource plugin >> directory scanner goes through these files and seems it loops and >> makes the build very slow in the best case and just locked in the >> worse one. >> >> Just in case you observe it, "find . -name '.gogradle' | xargs rm -Rf" >> solves it. >> >> Romain Manni-Bucau >> @rmannibucau | Blog | Old Blog | Github | LinkedIn >> > > -- > Jean-Baptiste Onofré > [email protected] > http://blog.nanthrax.net > Talend - http://www.talend.com
