From ivy-user-return-6386-apmail-ant-ivy-user-archive=ant.apache.org@ant.apache.org Wed Feb 10 20:22:30 2010 Return-Path: Delivered-To: apmail-ant-ivy-user-archive@www.apache.org Received: (qmail 78898 invoked from network); 10 Feb 2010 20:22:30 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 10 Feb 2010 20:22:30 -0000 Received: (qmail 55123 invoked by uid 500); 10 Feb 2010 20:22:29 -0000 Delivered-To: apmail-ant-ivy-user-archive@ant.apache.org Received: (qmail 55049 invoked by uid 500); 10 Feb 2010 20:22:29 -0000 Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ivy-user@ant.apache.org Delivered-To: mailing list ivy-user@ant.apache.org Received: (qmail 55039 invoked by uid 99); 10 Feb 2010 20:22:29 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Feb 2010 20:22:29 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [68.142.200.144] (HELO web30801.mail.mud.yahoo.com) (68.142.200.144) by apache.org (qpsmtpd/0.29) with SMTP; Wed, 10 Feb 2010 20:22:21 +0000 Received: (qmail 27854 invoked by uid 60001); 10 Feb 2010 20:21:59 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1265833319; bh=H3N0hekwqVFYNBXqg2kgbwJkIxQn6ghLGUtIH/aq+nQ=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=JnRKtr5NCxnS2Cvx7AxX9STDwZ9J1th7AeodYaQfDxQo4sM5tkxenmPWWugbN8pc6JDCZk147ORJ3AyXqrWGwff6fuFPVoFmSNP/6Wmt4927VlynKd5X1L8ajSl1B+chH4SJlW7x4xCg8KPVz9snU6VhuUlEqJm0/3ZUxmZSTww= DomainKey-Signature:a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=6fZ/lzdV2dKFjYDcUtyjGs9vr2enRjbxyXNc09AIzgUQD2N8ph9d6FQz3v+oPI7zwlxD+g9G6my2ybANE2yyeZ1Maim0naVTS123wodbxbLbgMJhqO2gGQEIjMa4f7hwwYPo3FVvqDIRua3JS0jG5PS9RLBjXlnJZUrbLMv6dpU=; Message-ID: <589156.27843.qm@web30801.mail.mud.yahoo.com> X-YMail-OSG: JpJokUQVM1nPFdViWxFDbMQDu7ocYS5_mwjatnGYnWlttb.oV4Zbhg.aPFtv1XwSCE3pacYdXOArdsOvdVvoHC.WkcXOSPsy2k1EPmJSLVoeDutBpuP8.z51HHzfvNtFfaWd7AGkiWxjg2lybySzNBQvQo2H4z4reSun6gHh8y4ocheg9Jy6PzzlLCSS9RDszYGo2O8AYMavDRxHKj1B0AiB41GjhCrxB9lyCMTKQJuEW1.jwKTMwGpZbWwatpqBuBMuJd.2B9C_CvaOJII19IwQ83gJub6HEooMctw7J8nyoj3fBoJDNbYjQvmIp459yKMuK0IY4mJGdjyGjeCkmUpf2q8_Mb76ACFHGaDF6Euainbm_BGSBCB_MIOb.PaGWD9jW__v2T9gvXEccFtOl9rSvCwSIamRE1KbTiaPnfNR4l8HzaouFQmu5V2WsDDBIvm.aUjOHIKYhmZia.VlNIRTz7ED2QtyHB88JzUDqeitU8dTSC6ttlVFT_qv.2HnXg2ShSXv6NPODqTDd3LfdcitNdkONgqi4x_qobNVATf_cZ8f62mwlI_fGYgXj_qxLIo9ODSd7DFICC0HWGZfK.j.NEvZYYsOABY0QQ1PU6yBlnIcY1MZWWLENZSZOAtMtHaKwE36b9mMOG7haOaGmrQ- Received: from [217.136.17.176] by web30801.mail.mud.yahoo.com via HTTP; Wed, 10 Feb 2010 12:21:59 PST X-Mailer: YahooMailRC/272.7 YahooMailWebService/0.8.100.260964 References: <27525526.post@talk.nabble.com> <7916a6a61002091939t54a66f43udd0f32dc0cdbbfda@mail.gmail.com> <27525922.post@talk.nabble.com> <7916a6a61002092057l6203e5d0lfa83b4d7c7f90797@mail.gmail.com> <27526318.post@talk.nabble.com> <27527071.post@talk.nabble.com> Date: Wed, 10 Feb 2010 12:21:59 -0800 (PST) From: Maarten Coene Subject: Re: Getting a module's artifacts for build To: ivy-user@ant.apache.org In-Reply-To: <27527071.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Thanks for the patch Carl, I've added a comment to the issue. Could you take a look? An alternative solution to your problem is using xmltask to find the artifacts defined by your ivy.xml. I use the approach myself in some of the build files @ work... Maarten ----- Original Message ---- From: Carl Quinn To: ivy-user@ant.apache.org Sent: Wed, February 10, 2010 8:36:32 AM Subject: Re: Getting a module's artifacts for build Aha, it looks like I'm not the first to ask for this: http://issues.apache.org/jira/browse/IVY-395 Maybe I'll just extend ivy:info itself and submit a patch. The actual Java code is pretty easy. Carl Quinn wrote: > > Good idea using properties, I might try that out. > > My main motivation for eliminating the duplication is that we have > hundreds of modules that I am convincing teams to convert to Ivy. If I can > move all the imperative logic to a common core of Ant imports, then all we > need in each project is the ivy.xml and maybe a tiny build.xml stub. Works > with Ant, and works with IvyDE and IntelliJ. A very easy sell if I can > pull it off :) > > I think I will try my hands at an Ivy plugin to add an extended info task. > > > > Mitch Gitman wrote: >> >> Carl, interesting use case. I can't think of any existing Ivy task that >> accomplishes what you're looking for. >> >> And I can't say I'd be motivated myself to go to the lengths you're going >> to >> to avoid redundancy. However, I can attest that I have run into trouble >> where I've changed the name of an artifact I'm publishing but I forgot to >> change the name in the ivy.xml. Then I'd be poring over an error message >> like: >> impossible to publish artifacts for [module]: java.io.IOException: >> missing >> artifact [artifact] >> >> This problem is strictly a matter of keeping track of the same name in >> two >> places. And the straightforward solution is to use a ${} Ant property >> placeholder for the artifact name in the ivy.xml--since property >> substitutions are allowed in source (unpublished) ivy.xml files. >> >> On Tue, Feb 9, 2010 at 7:54 PM, Carl Quinn wrote: >> >>> >>> Yes, I've had that part all figured out for awhile. I can build and >>> publish >>> all my simple projects now. >>> >>> What I would like to do next is to remove all knowledge of specific >>> artifacts from my Ant files, and derive the artifact build actions from >>> the >>> metadata already available in the ivy.xml file. (I don't like >>> redundancy) >>> >>> So, I would like to have something like Ivy:info that also gave me the >>> artifact declarations from my module's ivy file, including extra >>> attributes >>> if possible. All of that this is well before publish. I could then know >>> what >>> to build and put into the dist dir and then invoke publish on all of >>> that. >>> >>> Ideas? Or should I write a new Ivy Ant task? >>> >>> >>> >> >> > > -- View this message in context: http://old.nabble.com/Getting-a-module%27s-artifacts-for-build-tp27525526p27527071.html Sent from the ivy-user mailing list archive at Nabble.com.