Return-Path: Delivered-To: apmail-buildr-users-archive@www.apache.org Received: (qmail 29209 invoked from network); 15 Aug 2009 16:20:23 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 15 Aug 2009 16:20:23 -0000 Received: (qmail 6259 invoked by uid 500); 15 Aug 2009 16:20:30 -0000 Delivered-To: apmail-buildr-users-archive@buildr.apache.org Received: (qmail 6171 invoked by uid 500); 15 Aug 2009 16:20:29 -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 6160 invoked by uid 99); 15 Aug 2009 16:20:29 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 15 Aug 2009 16:20:29 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [209.85.220.213] (HELO mail-fx0-f213.google.com) (209.85.220.213) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 15 Aug 2009 16:20:20 +0000 Received: by fxm9 with SMTP id 9so1828777fxm.1 for ; Sat, 15 Aug 2009 09:19:59 -0700 (PDT) MIME-Version: 1.0 Received: by 10.239.145.34 with SMTP id q34mr178999hba.124.1250353199744; Sat, 15 Aug 2009 09:19:59 -0700 (PDT) Date: Sat, 15 Aug 2009 12:19:59 -0400 Message-ID: <153af7a10908150919k3dd0e373i9c63559933bc178a@mail.gmail.com> Subject: procedure and tips for creating a Buildr plugin? From: Shane Witbeck To: users@buildr.apache.org Content-Type: multipart/alternative; boundary=001485f6c60650885f0471308a70 X-Virus-Checked: Checked by ClamAV on apache.org --001485f6c60650885f0471308a70 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit I'm looking for docs (other than looking at existing plugins) to help me determine the steps for building a plugin. Does anything like this exist? Any tips in terms of what a complete plugin should have (ie. tests, etc.) before submitting it would be helpful as well. If formal docs on this topic don't already exist, I think this would be a big help to Buildr and it's users. Thanks, -Shane --001485f6c60650885f0471308a70--