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 trying to track this down but in the future it would be nice to just
flat out prevent this from happening.
Thoughts?
How are you doing your builds?
Is there a difference in your snapshot policy and release policy?
How are you controlling versions - parent POM dependency management?
How many people can deploy to your release repo? Snapshot repo?
If you are the only one, then no one else can trigger a release.
What Maven repo are you using?
Sorry for the questions but the answers might prompt some of the smarter
people to suggest good solutions.
Ron
--
Ron Wheeler
President
Artifact Software Inc
email: rwhee...@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
