Return-Path: X-Original-To: apmail-buildr-users-archive@www.apache.org Delivered-To: apmail-buildr-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 92BDC9956 for ; Thu, 10 Nov 2011 22:27:22 +0000 (UTC) Received: (qmail 3927 invoked by uid 500); 10 Nov 2011 22:27:22 -0000 Delivered-To: apmail-buildr-users-archive@buildr.apache.org Received: (qmail 3900 invoked by uid 500); 10 Nov 2011 22:27:22 -0000 Mailing-List: contact users-help@buildr.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@buildr.apache.org Delivered-To: mailing list users@buildr.apache.org Received: (qmail 3892 invoked by uid 99); 10 Nov 2011 22:27:22 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 10 Nov 2011 22:27:22 +0000 X-ASF-Spam-Status: No, hits=-0.1 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of rteabeault@rallydev.com designates 74.125.149.244 as permitted sender) Received: from [74.125.149.244] (HELO na3sys009aog118.obsmtp.com) (74.125.149.244) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 10 Nov 2011 22:27:16 +0000 Received: from mail-iy0-f182.google.com ([209.85.210.182]) (using TLSv1) by na3sys009aob118.postini.com ([74.125.148.12]) with SMTP ID DSNKTrxPsDhZfr0xoClzWZRcnxYcuvI3C2jB@postini.com; Thu, 10 Nov 2011 14:26:56 PST Received: by mail-iy0-f182.google.com with SMTP id l21so2716131iak.13 for ; Thu, 10 Nov 2011 14:26:55 -0800 (PST) MIME-Version: 1.0 Received: by 10.42.158.9 with SMTP id f9mr9844306icx.31.1320964015667; Thu, 10 Nov 2011 14:26:55 -0800 (PST) Received: by 10.42.230.198 with HTTP; Thu, 10 Nov 2011 14:26:55 -0800 (PST) In-Reply-To: References: Date: Thu, 10 Nov 2011 15:26:55 -0700 Message-ID: Subject: Re: Problem using build.yaml to specify groups of dependencies From: Russ Teabeault To: users@buildr.apache.org Content-Type: multipart/alternative; boundary=90e6ba21219bea387e04b168e66e --90e6ba21219bea387e04b168e66e Content-Type: text/plain; charset=ISO-8859-1 The docs for ArtifactNamespace.load show this exact thing where they create a named group called logging: logging: # define a named group - log4j:log4j:jar:1.2.15 - commons-logging:commons-logging:jar:1.1.1 and ArtifactNamespace.load is what is called to with the artifacts hash taken from build.yaml. So are the docs wrong or misleading? Thanks, -russ On Thu, Nov 10, 2011 at 2:45 PM, Peter Donald wrote: > Hi, > > On Fri, Nov 11, 2011 at 5:26 AM, Russ Teabeault > wrote: > > I am trying to use buildr.yaml to specify my dependencies > > > > artifacts: > > compile: > > - ant:ant:jar:1.6.5 > > - ant-contrib:ant-contrib:jar:1.0b2 > > - ... > > > > Based on everything I have read I should then be able to do > > > > compile.with artifact_ns[:compile] > > > > However, this fails in the artifacts method of artifact.rb since each > spec > > in the array is an ArtifactRequirement and there is no case handling that > > type. > > > > Is this a bug? Is there a better way to do this? What are other people > > doing? > > I don't think you can do this ... or at least I have never been able > to do this but it is a feature I have often desired ;) > > The way I end up doing it is > > > artifacts: > > ant: ant:ant:jar:1.6.5 > > ant_contrib: ant-contrib:ant-contrib:jar:1.0b2 > > compile.with :ant, :ant_contrib > > -- > Cheers, > > Peter Donald > --90e6ba21219bea387e04b168e66e--