This is worse when incorporated into a multi-module build: When the reactor builds B it is not guaranteed to use locally built A. If someone deployed to the repository, then it would use that one.
Is this an issue? Or have I missed something? -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Baptiste MATHUS Sent: 20 January 2009 12:56 To: Maven Users List Subject: Re: Interdependencies between modules Just a thought: use profile to disable your repository? Or simply work offline (mvn -o)? This way it will only use your local jar. Cheers. 2009/1/20 Richard Chamberlain <[email protected]> > Hi All, > > > > I've got a question about how maven works when there is a newer remote > library than a locally installed artefact. > > > > Say I've got project A and project B. B depends on A. > > > > - I build A and install it, to test that B will work with the > API changes in A. > > - If I build B it will use my locally built copy of A, > everything is fine > > > > UNLESS: The continuous integration tool builds a new copy of A after I > build A and install locally. When I come to build B it pulls in the > remote copy of A and my local change in A is ignored. > > > > How can I stop this happening as it does not give a predicatable build? > I really need to tell B to update its dependencies except for A. > > > > Thanks in advance, > > > > Rich > > > > -- Baptiste <Batmat> MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor ! --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
