This message was deleted.
# cachings
Slackbot
05/17/2023, 2:41 PMThis message was deleted.
v
Vampire
05/17/2023, 2:58 PMI personally always have the version to build hard-coded. I hate dynamically calculated versions, that are then dependent on VCS being present and usable for example. This makes builds non-reproducible and sometimes even not possible e.g. if JGit is used and you are in a Git worktree, or when building from source export, or when having a shallow clone, .... 🙂
But other than that, you should check why exactly the cache cannot be used. If you for example generate the version into a properties file that you pack as resource, you might need to configure the normalization and so on. If the version just influences the jar filenames I think it should not influence cacheability, but I might remember wrongly.
j
John
05/17/2023, 3:09 PMi can confirm that the jar file names do effect the cacheability
John
05/17/2023, 3:09 PMeven if contents are the same
John
05/17/2023, 3:09 PMi did a cache debug and saw it
John
05/17/2023, 3:09 PMthis is in the context of running tests on modules that depend on other modules (project dependencies) in the same build
t
Thomas Broyer
05/17/2023, 4:07 PMI like to set:
Copy code
tasks.withType<Jar>().configureEach {
// Never include the version in the JAR filenames
archiveVersion.set(null as String?)
}j
John
05/18/2023, 9:40 PMoh interesting
John
05/18/2023, 9:40 PMdoes that effect maven publishing?
t
Thomas Broyer
05/18/2023, 10:36 PMIt shouldn't, but I can't remember if I ever actually tried 🤷♂️
j
John
05/18/2023, 11:25 PMOk. Thanks for sharing ill investigate
John
05/19/2023, 6:31 PMYeah, i think it does mess up maven publishing. it can publish, but resolution will be messed up
John
05/19/2023, 6:34 PMactually i suspect its not the file name thats the problem for caching, but the contents. b/c the jar contains the manifest file that has the version number in it
t
Thomas Broyer
05/20/2023, 10:09 AMHa, sounds more logical! Have a look at https://docs.gradle.org/current/userguide/build_cache_concepts.html#filter_runtime_classpath then (but that means you're explicitly configuring the Jar tasks to add the version to the manifest, right?)
j
John
05/21/2023, 6:36 PMYeah we are
John
05/21/2023, 6:36 PMThat filter thing might be just what we need. Thanks!
John
05/22/2023, 1:35 PMhmm, caching is still not working. Now i am starting the file name matters as well
John
05/22/2023, 2:55 PMnope, not the name. there was another file i needed to exclude:
Copy code
normalization {
runtimeClasspath {
metaInf {
ignoreAttribute("Implementation-Version")
}
ignore("**/pom.xml")
}
}
}4 Views