Return-Path: Delivered-To: apmail-buildr-users-archive@www.apache.org Received: (qmail 12352 invoked from network); 7 May 2009 19:04:17 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 7 May 2009 19:04:17 -0000 Received: (qmail 97678 invoked by uid 500); 7 May 2009 19:04:16 -0000 Delivered-To: apmail-buildr-users-archive@buildr.apache.org Received: (qmail 97642 invoked by uid 500); 7 May 2009 19:04:16 -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 97632 invoked by uid 99); 7 May 2009 19:04:16 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 May 2009 19:04:16 +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 74.125.44.28 as permitted sender) Received: from [74.125.44.28] (HELO yx-out-2324.google.com) (74.125.44.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 May 2009 19:04:07 +0000 Received: by yx-out-2324.google.com with SMTP id 8so504313yxb.17 for ; Thu, 07 May 2009 12:03:45 -0700 (PDT) MIME-Version: 1.0 Received: by 10.151.121.12 with SMTP id y12mr5036369ybm.123.1241723024939; Thu, 07 May 2009 12:03:44 -0700 (PDT) In-Reply-To: <0022152d65599d89850469432e26@google.com> References: <0022152d65599d89850469432e26@google.com> Date: Thu, 7 May 2009 12:03:44 -0700 Message-ID: <5582dd3b0905071203h219876den5b84638cb25841ec@mail.gmail.com> Subject: Re: build.yaml issue From: Alex Boisvert To: users@buildr.apache.org Content-Type: multipart/alternative; boundary=001e680f1328cf9cd60469572ba9 X-Virus-Checked: Checked by ClamAV on apache.org --001e680f1328cf9cd60469572ba9 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit This works for me... and we also have tests (specs) for this so I'm thinking it's a user error. You may want to try: puts "Buildr.settings.build #{Buildr.settings.build.inspect}" to see the content of the loaded build.yaml and see if the 'project' property is defined. If you're still not getting what you want, send the content of your build.yaml. alex On Wed, May 6, 2009 at 12:12 PM, wrote: > Hello, > > I'm experiencing some issues with buildr. I have specified at build.yaml > file in the same directory as my buildfile.rb but when I try to reference it > in my buildfile it is does not get loaded. Currently, the only file that I > am able to reference is the settings.yaml file in the userhome/.buildr > directory. I also tried creating a profiles.yaml file and that too is not > referencable from within the buildfile. Has anyone experience this issue? > Here's a snippet of my buildfile. > > ENV['JAVA_OPTS'] ||= '-Xms512m -Xmx512m' > > require 'buildr' > > imSettings = Buildr.settings.user['insight_manager'] > raise 'You did not correctly setup your %USERPROFILE%/.buildr/settings.yaml > file' unless imSettings > > buildSettings = Buildr.settings.build['project'] > raise 'Could not find the build.yaml file!' unless buildSettings > > I've read the documentation on the website and I thinking I'm doing > everything right. The only thing I can think of is that there is a path > issue but I can't seem to find one. > > If you have any insight into what the problem might be I would greatly > appreciate it! > > Doug > --001e680f1328cf9cd60469572ba9--