> new jarB snapshot which causes things to break. How is that kind of thing > best avoided (other than forcing down locked version numbers?)
COMMUNICATION is the key. As a general practice, don't check in things that will break other people's stuff -- and if you must, do it in a branch, then let people know it is coming so they can plan to fix their stuff. If you are agreeing on interfaces (contracts) and building code that utilizes the interfaces, things should generally just work so long as you don't need to break those contracts. Continuous integration helps catch a lot of this, too. Wayne --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
