This message was deleted.
# develocity
s
This message was deleted.
d
We provide an example here of adding cacheability to particular Maven Enforcer rules: https://github.com/gradle/gradle-enterprise-build-config-samples/tree/main/build-caching-maven-samples/enforcer-project
c
Greatt ty
d
I think this section of the POM is adding the coordinates of each dependency as a goal input: https://github.com/gradle/gradle-enterprise-build-config-samples/blob/main/build-caching-maven-samples/enforcer-project/pom.xml#L137-L165
c
There's something left vague. In case of banned duplicate dependencies rules, how do i get the size of the dependencies list
d
I don't understand the question. Are you saying you want to add the size of the dependencies list as a goal input? Why would you need to do that, if you are adding the complete list of dependency coordinates?
c
Yeahh, i tried it, it's not working as expected. If i add the depedency coordinates as done in the samples you shared with me, the banned duplicate dependency rule is loaded from the cache even with duplicate dependencies in the pom.
I thought maybe if i add the size of the dependecy list would do the job, but i am still figuring it out
d
If you haven't yet, I would recommend enabling cache debugging.
Assuming you're a commercial Develocity customer, you can request support at support.gradle.com.
c
Deall ty