Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ivy-user@ant.apache.org
Received-SPF: pass (nike.apache.org: domain of jmagno.ti@gmail.com designates
 209.85.213.173 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=Mff65VFkBe7lIq/qk73IcQkaOaYDs4alL2zZzWc4/tje1JcYXP7hZrI1ofY/Vy3eec
         ltbVIOg09b8VL5n2KmH/1bk6uzsLjUX1XNiXfSgkXeE+VW8bmqvLucqkeHHaGSNgQboU
         BLG3p5eP1D1pinBHM40SVfHopcgdV8tmd6pGc=
MIME-Version: 1.0
In-Reply-To: 
 <4E7290A75A005841BB010749D2BB9EB00315F95D6A@PFGDSMMBX001.principalusa.corp.principal.com>
References: <BANLkTinkAcWpqGc675ZP7v=3GVR6E88XHA@mail.gmail.com>
	<4E7290A75A005841BB010749D2BB9EB00315F95D48@PFGDSMMBX001.principalusa.corp.principal.com>
	<BANLkTimsWdyy9oaZVPr-pVHp=+=x-C2U+w@mail.gmail.com>
	<4E7290A75A005841BB010749D2BB9EB00315F95D6A@PFGDSMMBX001.principalusa.corp.principal.com>
Date: Wed, 15 Jun 2011 09:37:50 -0300
Message-ID: <BANLkTim5b1E_pE=K_q=fYdVKeLcK01T_hw@mail.gmail.com>
Subject: Re: Transitive dependencies?
From: Jefferson Magno Solfarello <jmagno.ti@gmail.com>
To: ivy-user@ant.apache.org
Content-Type: multipart/alternative; boundary=00151750d9caa4ad7104a5bf6bda

--00151750d9caa4ad7104a5bf6bda
Content-Type: text/plain; charset=ISO-8859-1

Hi all, thanks all for the tips,

So, on my Project B, I have a distrib directory, from which I publish the
artifacts of Project B.

Let's suppose I have called <ivy:retrieve> on my Project B and that now I
have all the artifacts of Project A in the a 'lib' directory of Project B.
So now I have:

Project B root

   /distrib/B1.jar
   /distrib/B2.jar
   /distrib/B3.jar

   /lib/A1.jar
   /lib/A2.jar
   /lib/A3.jar

How can I use wildcards to publish those artifacts of Project A (lib
directory) without declaring them individually?

Thanks,

Jefferson


2011/6/14 Garner, Shawn <Garner.Shawn@principal.com>

> Cool, I didn't realize it was smart at all. Thanks for pointing it out.
> I thought it just created a list to iterate over.
>
> Shawn
>
> -----Original Message-----
> From: Not Zippy [mailto:notzippy@gmail.com]
> Sent: Tuesday, June 14, 2011 9:21 AM
> To: ivy-user@ant.apache.org
> Subject: Re: Transitive dependencies?
>
> Actually there is an ant tag which does a "smart" build "ivy:buildlist"
> will
> ensure that the builds are performed in the correct order.
>
> On Tue, Jun 14, 2011 at 9:15 AM, Garner, Shawn
> <Garner.Shawn@principal.com>wrote:
>
> > I don't know of a good way directly in Ivy.
> > If you use a build server like Jenkins you can trigger another build
> after
> > the build of the current project.
> >
> > Without a build server you would have to manually write an ant file that
> > builds project A, B, C in order.
> >
> > There is a Multi-project example in the samples section of the Ivy
> > distribution demoing this.  The website tutorial goes through it.
> >
> > Shawn
> >
> > -----Original Message-----
> > From: Jefferson Magno Solfarello [mailto:jmagno.ti@gmail.com]
> > Sent: Tuesday, June 14, 2011 8:43 AM
> > To: ivy-user@ant.apache.org
> > Subject: Transitive dependencies?
> >
> > Hello all,
> >
> > I have a multi-project setup like this:
> >
> > Project A publishs 5 artifacts
> >
> > Project B publishs 3 artifacts
> >
> > I would like to have a dependency in a way that Project B can publish its
> > own artifacts plus the artifacts of Project A.
> >
> > In the future maybe Proj A publishs more artifacts, I don't want to
> declare
> > the artifacts published by Proj A on the Ivy file of Proj B.
> >
> > I could have a Project C, that depends of project B, and when I execute
> > <ivy:retrieve> on project C, Ivy downloads all the artifacts published by
> B
> > (8 artifacts)
> >
> > Is there a way to do that?
> >
> > Regards,
> >
> > Jefferson
> >
> >
> > -----Message Disclaimer-----
> >
> > This e-mail message is intended only for the use of the individual or
> > entity to which it is addressed, and may contain information that is
> > privileged, confidential and exempt from disclosure under applicable law.
> > If you are not the intended recipient, any dissemination, distribution or
> > copying of this communication is strictly prohibited. If you have
> > received this communication in error, please notify us immediately by
> > reply email to Connect@principal.com and delete or destroy all copies of
> > the original message and attachments thereto. Email sent to or from the
> > Principal Financial Group or any of its member companies may be retained
> > as required by law or regulation.
> >
> > Nothing in this message is intended to constitute an Electronic signature
> > for purposes of the Uniform Electronic Transactions Act (UETA) or the
> > Electronic Signatures in Global and National Commerce Act ("E-Sign")
> > unless a specific statement to the contrary is included in this message.
> >
> > While this communication may be used to promote or market a transaction
> > or an idea that is discussed in the publication, it is intended to
> provide
> > general information about the subject matter covered and is provided with
> > the understanding that The Principal is not rendering legal, accounting,
> > or tax advice. It is not a marketed opinion and may not be used to avoid
> > penalties under the Internal Revenue Code. You should consult with
> > appropriate counsel or other advisors on all matters pertaining to legal,
> > tax, or accounting obligations and requirements.
> >
> >
>

--00151750d9caa4ad7104a5bf6bda--