maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yanko, Curtis" <curt_ya...@uhc.com>
Subject RE: The joys of dependencies
Date Fri, 05 Nov 2010 21:50:11 GMT
But in a CI system, the latest B is always built. In fact, in our Build Management system we
use push style dependencies instead of pull. So, instead of a build of A seeing in B needs
to be built, When B builds it tells A. In this way, any change will ultimately trigger all
of the dependent apps.

-----Original Message-----
From: Phillip Hellewell [mailto:sshock@gmail.com] 
Sent: Friday, November 05, 2010 5:20 PM
To: Maven Users List
Subject: Re: The joys of dependencies

On Fri, Nov 5, 2010 at 3:13 PM, Jon Paynter <kittle31@gmail.com> wrote:
> On Fri, Nov 5, 2010 at 1:57 PM, Phillip Hellewell <sshock@gmail.com> wrote:
>> In many of my cases, yes A actually does need C to compile.
>>
> In that case - my suggestion wont work for you.
>
> Also - after re-reading this thread it seems your assuming something 
> very simmilar to what I assumed when starting with maven:  namely ive 
> I have changed B while working on A, and I build from within project 
> A, maven will also pickup the changes from B -- this is not true.  
> What will actually happen is A will be compiled based on the last 
> installed version of B.  IMO the better option is to Always build from 
> the top level of your project, then changes across modules are always 
> built together with dependencies in the right order.

Actually, we don't use multi-module projects at all.  All our project/components live in their
own source trees in SVN and depend on each other using transitive dependencies.  So yeah,
building A can't possibly pick up a new version of B until B is built and installed/deployed.

Phillip

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


This e-mail, including attachments, may include confidential and/or
proprietary information, and may be used only by the person or entity
to which it is addressed. If the reader of this e-mail is not the intended
recipient or his or her authorized agent, the reader is hereby notified
that any dissemination, distribution or copying of this e-mail is
prohibited. If you have received this e-mail in error, please notify the
sender by replying to this message and delete this e-mail immediately.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Mime
View raw message