[Gradle] Do not try snapshotting non-existent classpath entries
The fix changes only Gradle's side of the transformation to be consistent with general Gradle behaviour for non-existent dependencies in classpath ^KT-62101 In Progress
This commit is contained in:
committed by
Space Team
parent
c5138b781f
commit
de04c62df5
+2
@@ -71,6 +71,8 @@ abstract class BuildToolsApiClasspathEntrySnapshotTransform : TransformAction<Bu
|
||||
checkVersionConsistency()
|
||||
}
|
||||
val classpathEntryInputDirOrJar = inputArtifact.get().asFile
|
||||
if (!classpathEntryInputDirOrJar.exists()) return
|
||||
|
||||
val snapshotOutputFile = outputs.file(classpathEntryInputDirOrJar.name.replace('.', '_') + "-snapshot.bin")
|
||||
|
||||
val granularity = getClassSnapshotGranularity(classpathEntryInputDirOrJar, parameters.gradleUserHomeDir.get().asFile)
|
||||
|
||||
Reference in New Issue
Block a user