Return-Path: Delivered-To: apmail-buildr-users-archive@www.apache.org Received: (qmail 67324 invoked from network); 19 Aug 2009 00:48:21 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 19 Aug 2009 00:48:21 -0000 Received: (qmail 64400 invoked by uid 500); 19 Aug 2009 00:48:40 -0000 Delivered-To: apmail-buildr-users-archive@buildr.apache.org Received: (qmail 64337 invoked by uid 500); 19 Aug 2009 00:48:40 -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 64327 invoked by uid 99); 19 Aug 2009 00:48:40 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Aug 2009 00:48:40 +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: domain of boisvert@intalio.com designates 209.85.211.173 as permitted sender) Received: from [209.85.211.173] (HELO mail-yw0-f173.google.com) (209.85.211.173) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Aug 2009 00:48:30 +0000 Received: by ywh3 with SMTP id 3so5767791ywh.22 for ; Tue, 18 Aug 2009 17:48:08 -0700 (PDT) MIME-Version: 1.0 Received: by 10.151.20.18 with SMTP id x18mr9234792ybi.7.1250642888031; Tue, 18 Aug 2009 17:48:08 -0700 (PDT) In-Reply-To: References: Date: Tue, 18 Aug 2009 17:48:08 -0700 Message-ID: <5582dd3b0908181748n2cd19e79na3d59cc240fb3b8b@mail.gmail.com> Subject: Re: Problem with _1.3.4_ while running release task From: Alex Boisvert To: users@buildr.apache.org Content-Type: multipart/alternative; boundary=000e0cd4b31a14fde0047173fd18 X-Virus-Checked: Checked by ClamAV on apache.org --000e0cd4b31a14fde0047173fd18 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit This appears to be a bug. I was under the impression the _1.3.4_ convention to select a version was universal across platforms but apparently it's not. (I didn't find any documentation on this... if anybody has pointers, I'd very grateful) I've created https://issues.apache.org/jira/browse/BUILDR-303 to track this. The workaround using -V doesn't actually fix the issue; it happens to work but does not ensure the same buildr version is used for releasing. alex On Tue, Aug 18, 2009 at 4:37 PM, Joel Muzzerall wrote: > I am trying to run > > buildr release > > but it produces this error: > > /usr/bin/ruby1.8 -S buildr _1.3.4_ --buildfile *snip* --environment > development clean upload DEBUG=no > (in *snip*, development) > Buildr aborted! > Don't know how to build task '_1.3.4_' > > I believe that this syntax should work. Any idea why it doesn't? > > I can work around this issue by changing lib/buildr/core/build.rb:270 from > > args = '-S', 'buildr', "_#{Buildr::VERSION}_", '--buildfile', > release_candidate_buildfile > > to > > args = '-S', 'buildr', "-V#{Buildr::VERSION}", '--buildfile', > release_candidate_buildfile > > -- > Joel Muzzerall > Computer Systems Analyst > Intalio > > 415-519-6747 > --000e0cd4b31a14fde0047173fd18--