It's simply to save time. Let's say you have a project containing of several components. Instead of releasing every component separate, you perform the release only for the main component and in a transitive way maven performs automatically releases of all dependent SNAPSHOT components. Naturally this process includes compiling and running tests.
But maybe it is better to use a multi module project (in which SNAPSHOT dependencies between submodules are resolved by maven) for this kind of project structure. Regards, Abid -------- Original-Nachricht -------- > Datum: Fri, 23 Sep 2011 12:23:21 -0400 > Von: Ron Wheeler <[email protected]> > An: Maven Users List <[email protected]> > Betreff: Re: release transitive SNAPSHOT dependency > I hope not! > Sounds like a really bad thing to do. > How does maven know that B is release quality? > > Ron > > On 23/09/2011 11:58 AM, Abid Hussain wrote: > > Hello, > > > > e.g. there is a project A (e.g. 1.0-SNAPSHOT) which has a dependency to > another non-released project B (e.g. 2.3-SNAPSHOT). > > > > AFAIK performing a release which has SNAPSHOT versions is not possible. > > > > Is there a way to tell maven that when a release of project A should be > performed to automatically > > - perform a release of B (e.g. 2.3) > > - update the dependency from A to B (so that A is dependent to B 2.3) > > - and then actually perform the release of A (resulting in A 1.0)? > > > > Regards, > > > > Abid > > > -- > Ron Wheeler > President > Artifact Software Inc > email: [email protected] > skype: ronaldmwheeler > phone: 866-970-2435, ext 102 > > -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
