I don't know if this affects JGit's garbage collection but it does affect SmartGit on Windows (not sure if that uses native GC or JGit's).
Long file names of grafico XML files can occur if there are nested folders. If this is the case then GC will throw an error such as:
unable to access 'model/business/29a46746-2d2d-433f-8165-f3128b76f716/75afd475-667c-4311-bcbc-b59f66b93db0/3dc49c7a-ec81-4f77-99ed-f8b990155374/795c87c1-4996-4846-bdfe-22ce80cd8ef5/4de77580-e163-42e5-856b-a859b1d73c10/.gitattributes': Filename too long
I've added longpaths=true to the git config file for new repos and this fixes the issue, but not sure if there are any side effects so leaving this issue open.
I don't know if this affects JGit's garbage collection but it does affect SmartGit on Windows (not sure if that uses native GC or JGit's).
Long file names of grafico XML files can occur if there are nested folders. If this is the case then GC will throw an error such as:
unable to access 'model/business/29a46746-2d2d-433f-8165-f3128b76f716/75afd475-667c-4311-bcbc-b59f66b93db0/3dc49c7a-ec81-4f77-99ed-f8b990155374/795c87c1-4996-4846-bdfe-22ce80cd8ef5/4de77580-e163-42e5-856b-a859b1d73c10/.gitattributes': Filename too long
I've added
longpaths=true
to the git config file for new repos and this fixes the issue, but not sure if there are any side effects so leaving this issue open.