Mailing-List: contact ivy-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ivy-user@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of gscokart@gmail.com designates
 64.233.166.182 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        b=qXAfBqZxxwA3OIdZgq6ZKSEXY4Q95S/dLBWiZ88RAL+rEroNB9vKGD16ObiSVzc993Kxk3Sw5e30AQCnpYtiAsCrXsLK2YIlJ2/co0NwQvCpgCY2c1pf5EXZG1HWSCQQLmGGR3vYoMltxQ4Z9/j94/iy7hTdALRosNTTDsV9b1s=
Message-ID: <e9d8a2610712202334q77d63604n913ce01ceab945ed@mail.gmail.com>
Date: Fri, 21 Dec 2007 08:34:26 +0100
From: "Gilles Scokart" <gscokart@gmail.com>
To: ivy-user@incubator.apache.org
Subject: Re: Deploying a Project(s)
In-Reply-To: <c1f334c80712200935x46deebr31546cb370c95d6c@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_25129_13812442.1198222466724"
References: <c1f334c80712191549p8a031bax23b559a0c911324@mail.gmail.com>
	 <4769C500.3060701@cpphacker.co.uk>
	 <c1f334c80712200935x46deebr31546cb370c95d6c@mail.gmail.com>

------=_Part_25129_13812442.1198222466724
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

You will have the 1.1 version that will be taken.  The 1.0 will be reported
as evicted.  I think you see that in the ant console.  I'm sure you see it
in the XML report of the resolution.

Gilles

2007/12/20, Roger Kapsi <roger.kapsi@mogulus.com>:
>
> Cool,
>
> how do you avoid the following situation though.
>
> subproject1 depends on commons-logging-1.1.jar
> subproject2 depends on commons-logging-1.0.jar
>
> The latter is an accident because I forgot to update subproject2's
> dependencies. I was hoping Ivy could help me in the deployment process and
> warn me if my subprojects refer to different versions of the same
> artifact.
>
> Roger
>
> On Dec 19, 2007 8:27 PM, Phillip Rhodes <mindcrime@cpphacker.co.uk> wrote:
>
> > Roger Kapsi wrote:
> >
> > > And I want to tell Ivy or rather Ant to give me C and all its
> > > dependencies. In other words I want to get C.jar, B.jar, A.jar and all
> > > the other external Jars. Hope somebody can give me a hint how to do
> > > that or am I on the wrong track with Ivy?
> >
> > There may be a cleaner way, but here's what I do:
> >
> > 1. in each sub-project, resolve the dependencies to the local "lib" dir
> > with configurations separating the dependencies that are needed at
> > runtime from the ones that arent'. So I wind up with something like
> >
> > /myproject/subproject1/lib
> >                        /core/
> >                           ajar.jar
> >                           bjar.jar
> >                        /compile/
> >                           compileonly1.jar
> >                           compileonly2.jar
> >
> >
> > 2. in the "package" task for each sub-project (it probably more properly
> >  belongs in "publish" but I'm still tweaking this) copy all of the
> > "runtime" jars (the "core" directory) to a common dir
> >
> > so I have something like this:
> >
> > /myproject/
> >    subproject1/
> >    subproject2/
> >    subprojectN/
> >    commonlib/ :this contains all the dependent jars for all subprojects
> >
> > 3. then in the "master" project I just declare dependencies on the
> > artifacts from the subprojects like normal and resolve them to a dir
> > I call "assemble."  The I copy everything from the commonlib dir into
> > the "assemble" dir and package it.  In my case the subprojects are
> > typically building war files or ejb-jar files and the driver builds
> > an ear, but the same approach could be used for other things I guess.
> >
> > Again, there might be a better way, but this seems to work for now.
> > HTH.
> >
> >
> > TTYL,
> >
> >
> > --
> > Phillip Rhodes
> > Chief Architect - OpenQabal
> > https://openqabal.dev.java.net
> >
>


-- 
Gilles Scokart

------=_Part_25129_13812442.1198222466724--