Mailing-List: contact users-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Maven Users List" <users@maven.apache.org>
Received-SPF: pass (athena.apache.org: local policy)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: The joys of dependencies
Date: Fri, 5 Nov 2010 16:50:11 -0500
Message-ID: 
 <2007E972E904A240B02B1C0E754EE5BD0AB8D682@APSW0639EVS.ms.ds.uhc.com>
In-Reply-To: <AANLkTi=nGHs95AzsMV+94RJK5rq1hPKkU_==Uj9tEf9r@mail.gmail.com>
Thread-Topic: The joys of dependencies
Thread-Index: Act9L2W+RKo7ASl4Qd2O20BnaNcBQQAA6RSA
References: <AANLkTi=NZM-pLGXq3NjZ6s=H7kuKsxJs9TxTo+jj1Umo@mail.gmail.com>
 <AANLkTindHnBZqpSOn61tn8jVH8KTJEC1OAajkDsVRje9@mail.gmail.com>
 <AANLkTikQA2hCPeZQqb7v7wvgvDKTuXDWnF8mGPOeyJx7@mail.gmail.com>
 <AANLkTin6h+dprh+JmFvNbatk79j7scgXh11NiXR99AqS@mail.gmail.com>
 <AANLkTimrRyzTpujcMHwfsKiQaw3cKdLy2DK=fgZSkUxj@mail.gmail.com>
 <AANLkTi=nGHs95AzsMV+94RJK5rq1hPKkU_==Uj9tEf9r@mail.gmail.com>
From: "Yanko, Curtis" <curt_yanko@uhc.com>
To: "Maven Users List" <users@maven.apache.org>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

But in a CI system, the latest B is always built. In fact, in our Build Man=
agement 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]=20
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> wrot=
e:
>> 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=20
> very simmilar to what I assumed when starting with maven: =A0namely ive=20
> I have changed B while working on A, and I build from within project=20
> A, maven will also pickup the changes from B -- this is not true. =A0
> What will actually happen is A will be compiled based on the last=20
> installed version of B. =A0IMO the better option is to Always build from=20
> the top level of your project, then changes across modules are always=20
> built together with dependencies in the right order.

Actually, we don't use multi-module projects at all.  All our project/compo=
nents 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