I have an issue where using `zipTree` on a jar file from compile dependencies causes pathnames that ...

# gradle

[Dico]

I have an issue where using zipTree on a jar file from compile dependencies causes pathnames that exceed the windows MAX_PATH limit of 260 characters. On my local machine it is fine, but my gradle CI machine has the project cloned on a slightly longer root path.

I'm using it for proguard tasks a bit like this -

val (obfuscatedClassFiles, exemptedClassFiles) = obfuscationIncludedJars
    .fold(files().asFileTree) { acc, jar -> acc + zipTree(jar) }
    .let { Pair(it.matching { exclude(*programClassesThatSkipProguard) }, it.matching { include(*programClassesThatSkipProguard) }) }

[bjonnh]

(because the current PATH is used in the set variable)

[Dico]

I don't think shadowjar is the solution, I think I'll use a jar task for this and use include/exclude on the task instead of the filetree as a workaround

[bjonnh]

https://github.com/gradle/gradle/issues/1989#issuecomment-550192866