Hi Jo, The main idea is: - I change C, and install it to the repository - When working with A, I do not get the changes in C
If I working with jar-s, and A is transitively dependent on C, then if a new C is installed into the repository, I will get the new version. But with war - it does not count the transitive dependencies, so I does not get the changes. Regards, Péter -----Original Message----- From: Jo Vandermeeren [mailto:[EMAIL PROTECTED] Sent: Friday, June 08, 2007 11:01 AM To: Maven Users List Subject: Re: War plugin transitive dependency On 6/7/07, Váry Péter <[EMAIL PROTECTED]> wrote: > > With using the war plugin, we can declare transitive dependencies, A > depends on B, and B depends on C. With SNAPSHOT versions I would like to see > every changes in C appear immediately in A, without any manual interaction > (or as few as possible). Hi Peter, Maven depends on artifacts which installed in your repository. When depending on SNAPSHOT versions, Maven will use that latest installed (or deployed, determined by the check interval) version of the dependency. So, if you have made changes in C, don't expect B and A to see them, unless module C has been (re)installed in the repository. When you build from a common parent (which contains A, B and C as modules), Maven will order the module's build based upon defined dependencies between them. This is why builds started from the parent level, can guarantee that B and A will see the latest changes made in C. Cheers Jo --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
