Hi, The situation you describe look very similar to ours. We use the maven release plugin.
but we had problems with versions: warA has dep to jarB version 1 which has dep to jarC version1 warA has also dep to JarD version 1 which has dep to jarC version 2. when warA is build, only version 1 of jarC is included. This causes JarD to fail runtime. To solve this, I created a plugin called deptools ( http://github.com/mbknor/deptools) which would fail the building og warA telling you that jarC version 2 was needed but not included. maybe this plugin, can help you too. -Morten On Sun, May 23, 2010 at 3:36 AM, Wayne Fay <[email protected]> wrote: > > 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: [email protected] > For additional commands, e-mail: [email protected] > >
