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 03D6B67AD for ; Wed, 27 Jul 2011 06:28:08 +0000 (UTC) Received: (qmail 21522 invoked by uid 500); 27 Jul 2011 06:28:07 -0000 Delivered-To: apmail-buildr-users-archive@buildr.apache.org Received: (qmail 21361 invoked by uid 500); 27 Jul 2011 06:28:00 -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 21346 invoked by uid 99); 27 Jul 2011 06:27:58 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Jul 2011 06:27:58 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW X-Spam-Check-By: apache.org Received-SPF: unknown (athena.apache.org: error in processing during lookup of chris@edatasource.com) Received: from [209.85.215.44] (HELO mail-ew0-f44.google.com) (209.85.215.44) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Jul 2011 06:27:52 +0000 Received: by ewy19 with SMTP id 19so1963149ewy.17 for ; Tue, 26 Jul 2011 23:27:30 -0700 (PDT) MIME-Version: 1.0 Received: by 10.213.104.131 with SMTP id p3mr1230700ebo.10.1311748050228; Tue, 26 Jul 2011 23:27:30 -0700 (PDT) Received: by 10.213.27.66 with HTTP; Tue, 26 Jul 2011 23:27:30 -0700 (PDT) Date: Wed, 27 Jul 2011 01:27:30 -0500 Message-ID: Subject: Packaging Shortcuts From: Chris Adams To: users@buildr.apache.org Content-Type: multipart/alternative; boundary=0015174c0dc29196d104a907247b --0015174c0dc29196d104a907247b Content-Type: text/plain; charset=ISO-8859-1 Hi, I'm making good progress migrating our build from ant to buildr, but there's one thing I'm still having a difficult time figuring out how to do. The way my project is laid out is in the following hierarchy (for example): root-project ---- library 1 ---- library 2 ---- webapp1 ---- webapp2 Right now, to build and package webapp 2 from the root directory, the user has to fully qualify it: > buildr root-project:webapp2:package What I'd really like is for our developers to simply type the following from the root: > buildr webapp2 package > buildr webapp1 package etc. Is this possible? Or do they always have to qualify it with project:sub-project:package? Thanks. - Chris --0015174c0dc29196d104a907247b--