On 13/10/2015 2:08 PM, Kevin Burton wrote:
I want to lock in the effective classpath for our releases.
So if extra .jars or versions of .jars are changed, I want the build to
fail until I manually approve it.
For some reason, our version of cassandra regressed and broke on release.
Still
Users List <users@maven.apache.org>
Sent: Di., 13 Okt. 2015 20:09
Subject: Best way to lock in .jar versions between releases.
I want to lock in the effective classpath for our releases.
So if extra .jars or versions of .jars are changed, I want the build to
fail until I manually approve i
Forget transitive dependencies. Pretend you're back on Ant. All
artifacts must be declared. Leave nothing to chance.
Declare all dependencies, including the ones you are currently
bringing in transitively, in your project's pom.
Set all versions with [1.2.3] to "lock" them down.
There may be
I want to lock in the effective classpath for our releases.
So if extra .jars or versions of .jars are changed, I want the build to
fail until I manually approve it.
For some reason, our version of cassandra regressed and broke on release.
Still trying to track this down but in the future it
Wow. Lots of questions!
I ended up working around this by just writing a post build script that
generates a build fingerprint of our .jars
I then commit the fingerprint. If a build changes the fingerprint then we
can't push.
It's kind of ugly but we unfortunately have a post build script
