Dependency versions and repeatable builds

I’ve often specified dependency versions dynamically for example in ivy.xml files, without the thought that without further efforts this prevents exactly repeatable builds of projects.

That “2.+” (for latest 2.x sub-revision) on a JAR dependency may well not resolve to the same revision in a few weeks when you do a build to test a bug fix.

It’s something to keep in mind given the mix of dependencies that typically end up in a project, and the possibility of bugs and changes that can be introduced in newer versions of these.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s