- Can these 2 differences, marked as IGNORED influence the calculation of the build cache key?
Yes, the IGNORED is the path sensitivity.
That does not change that the content of the file is considered input.
If yes, is it possible to “normalize” jars created by a transformation?
As it is a cacheable transform, I’d guess that the transform should have been taken from cache too. Maybe the inputs for the transform were different?
How the jar file is normalized depends on where the jar is used.
If the input it is used for for example is @Classpath or @CompileClasspath, things like timestamps or file order in the jar is normalized. If it is used as @InputFile, then the file’s actual bytes are the input. In the latter case, the transform would have to make sure to generate binary-identical results, or you would need to chain another transform in, that does the normalization after the actual transform did run.
Nevertheless, it’d be strange that only these two jars have different keys, and the rest jars are precisely the same
Could for example be that - as it is a cacheable transform - you had those two already built locally and put to your cache and the others were retrieved from the remote cache or something like that.