"heiko.braun(a)jboss.com" wrote : Acceptance test is one thing, but having to release every dependency because of minor version upgrade (which IMO is supposed to be compatible) is not a way to go either. | | If you don't favor ranges you could be explicit with compatible versions instead. Suppose the following: AS 5.0 depends on EJB3 [1.0,2.0) EJB3 1.0 depends on MetaData [1.0,2.0) Current MetaData is 1.0. Now I release MetaData 1.1 for AS trunk. scott.startk(a)jboss.org wrote : The mvn release plugin should be recording the versions used, and that version info committed as part of the tag. The release build should effectively be locked to single versions. In the repo it should have been noted as: AS 5.0-1 -> EJB3 1.0-1 EJB3 1.0-1 -> MetaData 1.0-1 To update the repo an EJB3 1.0 release must be done: EJB3 1.0-2 -> MetaData 1.1-1. At which point AS 5.0-1 -> EJB3 1.0-1 -> MetaData 1.0-1 is reproducable. Followed by AS 5.0 release: AS 5.0-2 -> EJB3 1.0-2. Ivy works that way and so should Maven. But I don't see how it works with Maven and transitive dependencies. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4136694#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...