JLBP-14 additional reason

Today I discovered a new reason why "Specify a single, overridable version of each dependency" is a good idea. If you're doing actual research, this is necessary to ensure reproducible results. Otherwise, results shift over time, or even from one month to the next.

FWIW this bit me in Python where version pinning is less common, but it applies equally to Java.

The issue does not name a file, test, or entry point. Start by locating the documentation for JLBP-14, “Specify a single, overridable version of each dependency,” and review how its rationale is presented. Done means the reproducibility concern is incorporated without changing the recommendation’s meaning.

Rédigé par le modèle d'indexation à partir du texte de l'issue.