Return-Path: Delivered-To: apmail-incubator-ivy-user-archive@locus.apache.org Received: (qmail 6239 invoked from network); 26 Apr 2007 13:15:51 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 26 Apr 2007 13:15:51 -0000 Received: (qmail 88122 invoked by uid 500); 26 Apr 2007 13:15:57 -0000 Delivered-To: apmail-incubator-ivy-user-archive@incubator.apache.org Received: (qmail 88107 invoked by uid 500); 26 Apr 2007 13:15:57 -0000 Mailing-List: contact ivy-user-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ivy-user@incubator.apache.org Delivered-To: mailing list ivy-user@incubator.apache.org Received: (qmail 88098 invoked by uid 99); 26 Apr 2007 13:15:57 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 Apr 2007 06:15:57 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: local policy) Received: from [209.191.106.88] (HELO web39504.mail.mud.yahoo.com) (209.191.106.88) by apache.org (qpsmtpd/0.29) with SMTP; Thu, 26 Apr 2007 06:15:48 -0700 Received: (qmail 20099 invoked by uid 60001); 26 Apr 2007 13:15:28 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=iUNYUNyyICZGb4zeIsfH8pGGRLixXAUxhGEbDXWGtIYGPu/JDc4n9QV1Vfllb8aPVYt6c+q+RhEfTi0wnN/SnECIHwGdUEBOlFzn5rmtLG9X1uuBVjjYaCY5DFcKnmSuH0r689hD+NkiL606S7gq+a7oeeUhfVmU9vyUlTvLXfo=; X-YMail-OSG: O3Snp2cVM1lj2dxzBuxXI9KeWV6NHOWgHOWDCVQCxelyLX5G5rJaBityOVvTa6onEKLdvA9OjEw1kR8bJ75BHBKmtDPQukCNSchT.YY9Xfa4cuimp8tuye5JLeebXQ-- Received: from [192.18.43.225] by web39504.mail.mud.yahoo.com via HTTP; Thu, 26 Apr 2007 06:15:28 PDT Date: Thu, 26 Apr 2007 06:15:28 -0700 (PDT) From: jeff Subject: Re: publish two artifacts from single project To: ivy-user@incubator.apache.org In-Reply-To: <635a05060704260028k5d1812dblb8e7d2479f96c054@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-987439520-1177593328=:19280" Content-Transfer-Encoding: 8bit Message-ID: <123855.19280.qm@web39504.mail.mud.yahoo.com> X-Virus-Checked: Checked by ClamAV on apache.org --0-987439520-1177593328=:19280 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit i did try this, and it results in the two JARs being published to the same artifact ... the latter simply overwrites the former ... for examples ... [ivy:publish] :: publishing :: [ com.sun.portal | admin ] [ivy:publish] published ps_util to /home/jtb/src/ps.trunk/admin/../dependencies/private-repository/com.sun.portal/admin/7.2/admin-7.2.jar [ivy:publish] published admin_common to /home/jtb/src/ps.trunk/admin/../dependencies/private-repository/com.sun.portal/admin/7.2/admin-7.2.jar [ivy:publish] published ivy to /home/jtb/src/ps.trunk/admin/../dependencies/private-repository/com.sun.portal/admin/ivys/ivy-7.2.xml two JARs, ps_util.jar and admin_common.jar. they are indeed both published, but to the same JAR in the repo, admin-7.2.jar. looking at that JAR, it contains the contents of admin_common.jar, not ps_util.jar maybe i did not make it clear what i was trying to accomplish. i want to publish two artifacts, what i want is from the "admin" project, to publish two artifacts, com.sun.portal/admin_common com.sun.portal/util there are different artifacts, i do NOT want a single artifact with two JARs (which i *think* what the example you gave is supposed to accomplish, but it didn't seem to work like that). any ideas? Xavier Hanin wrote: On 4/26/07, jeff wrote: > i did find a hack to accomplish this ... which was to create a new build file that just had the ant code to publish the second artifact. note from my previous email that i had to set ivy.dep.file in the seconard build file. You don't need to call publish twice to do what you want, but rather use tokens in your publication pattern: organisation="com.sun.portal" module="admin" revision="${PS.product.version}" pubdate="${pubdate}" status="integration" overwrite="true" > HTH, Xavier > > i needed to publish the secondary artifact in a separate ant file, i am guessing because once the primary ivy.xml is loaded, i could not overwrite the variables setup by it to point to the primary artifact. > > is there some better way to accomplish this? > > jeff wrote: i have one project (one build.xml), that generates multiple JARs that i wish to publish. i can't find the right approach to this. > > i've tried too many permutations to list here, but this is the latest i have tried ... > > my two artifacts ... > > > > > > > > and ... > > > organisation="com.sun.portal" > module="admin" > revision="${PS.product.version}" > pubdate="${pubdate}" > status="integration" > overwrite="true" > > > > > > > thus publishes both of the JARs, but both as the same name, admin-7.2.jar, so one overwrites the other. > > any ideas? > > > > > --------------------------------- > Ahhh...imagining that irresistible "new car" smell? > Check outnew cars at Yahoo! Autos. > > > > --------------------------------- > Ahhh...imagining that irresistible "new car" smell? > Check outnew cars at Yahoo! Autos. -- Learn Ivy at ApacheCon: http://www.eu.apachecon.com/ Manage your dependencies with Ivy! http://incubator.apache.org/ivy/ --------------------------------- Ahhh...imagining that irresistible "new car" smell? Check outnew cars at Yahoo! Autos. --0-987439520-1177593328=:19280--