I’m trying to identify strategies to govern how Gradle handles locally published snapshots taking priority over centrally published snapshots.
Say I have project ‘A’ depending on project ‘B’, and both are published to my shared object repository.
I want to publish B.jar locally and have A pick up those local changes, ignoring the B.jar that gets resolved out of the shared repository.
I never used Maven much but I’m told this is fairly transparent in Maven. In Ivy, this behavior was possible, but hairy to implement… basically people usually chain the local and remote repository and then fiddle with Ivy’s 100 different knobs to make the local artifact take priority in whatever way is desired.
It was hairy and buggy and never totally satisfactory.
Am I talking about ‘project dependencies’ here?
What knobs are there to control this behavior, like say to prevent a stale local artifact from hanging around too long?