Skip to content

General Use Pattern

Jump to bottom
Roberto Perez Alcolea edited this page Mar 13, 2024 · 3 revisions
  1. Daily locking of dynamic dependencies
    • Run a daily job to lock your dependencies. Every day before you show up to work you can have an automated system to pull in the latest dependencies and run your tests. If they pass, your team has a stable dependency graph for the day. If they fail you can have a subset of the team deal with the dependency issues while the rest keep with what they're were doing using yesterday's dependency lock.
    • Occasionally (and optionally) run updateLock to try out a single new dependency.
  2. Lock on release
    • When you're ready to cut that shiny new version of your software create a lock of your dependencies. You'll be able to recreate the exact state of your dependency graph if you ever need to reproduce a build.
  3. Deal with IDE issues
    • Create a lock with generateLock saveLock.
    • Watch as you no longer have to deal with one subproject depend on an old version and mess up another's dependency graph
    • Stop WAR deployments from copying 2 different versions of a dependency into the directory.
Clone this wiki locally