Return-Path: Delivered-To: apmail-incubator-buildr-user-archive@locus.apache.org Received: (qmail 10415 invoked from network); 3 Jul 2008 18:58:43 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 3 Jul 2008 18:58:43 -0000 Received: (qmail 27599 invoked by uid 500); 3 Jul 2008 18:58:43 -0000 Delivered-To: apmail-incubator-buildr-user-archive@incubator.apache.org Received: (qmail 27577 invoked by uid 500); 3 Jul 2008 18:58:43 -0000 Mailing-List: contact buildr-user-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: buildr-user@incubator.apache.org Delivered-To: mailing list buildr-user@incubator.apache.org Received: (qmail 27566 invoked by uid 99); 3 Jul 2008 18:58:43 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Jul 2008 11:58:43 -0700 X-ASF-Spam-Status: No, hits=2.7 required=10.0 tests=HTML_MESSAGE,SPF_SOFTFAIL X-Spam-Check-By: apache.org Received-SPF: softfail (athena.apache.org: transitioning domain of boisvert@intalio.com does not designate 64.233.184.226 as permitted sender) Received: from [64.233.184.226] (HELO wr-out-0506.google.com) (64.233.184.226) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Jul 2008 18:57:53 +0000 Received: by wr-out-0506.google.com with SMTP id c53so695934wra.20 for ; Thu, 03 Jul 2008 11:58:11 -0700 (PDT) Received: by 10.150.145.20 with SMTP id s20mr794649ybd.242.1215111491721; Thu, 03 Jul 2008 11:58:11 -0700 (PDT) Received: by 10.151.110.18 with HTTP; Thu, 3 Jul 2008 11:58:11 -0700 (PDT) Message-ID: <5582dd3b0807031158p6ae3a8c2k5b953028d238e87@mail.gmail.com> Date: Thu, 3 Jul 2008 11:58:11 -0700 From: "Alex Boisvert" To: buildr-user@incubator.apache.org Subject: Re: Testing out Buildr 1.3.2 gem install In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_11996_10060940.1215111491723" References: <3de5d7d20807020948k4b34c6fbh2eb4527347cd86e4@mail.gmail.com> <153af7a10807021042r5c6f4f0cm6f39c30599126dc@mail.gmail.com> <5582dd3b0807021431v4b82622bid5c795efc48a7502@mail.gmail.com> <5582dd3b0807031123u4d2ac6dcy527517d4c932c2b9@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_11996_10060940.1215111491723 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Ok, I'll go with "buildr scala-init" for now and enable Scala support only if all the necessary artifacts are available during bootstrap. alex On Thu, Jul 3, 2008 at 11:46 AM, Assaf Arkin wrote: > Unfortunately the boot classpath is highly guarded so we can't add to it > after we start the vm, and we do that fairly early. > > So we need a way for Scala to grab its dependencies without having to hack > the buildfile. > > > On Jul 3, 2008, at 11:23 AM, "Alex Boisvert" wrote: > > On Wed, Jul 2, 2008 at 10:40 PM, lacton >> wrote: >> >> This issue has come up frequently enough now that it might be worth >>>> disabling Scala support unless the necessary artifacts are already >>>> >>> available >>> >>>> locally. One could then explicitly download Scala artifacts by doing >>>> something like "buildr scala-support" as a one-time initialization. >>>> >>>> Thoughts? >>>> >>> >>> My best idea is that buildr waits until it absolutely needs Scala >>> support before trying to download the Scala-related artifacts. E.g., >>> when finding a scala source file during compile, when finding an >>> explicit reference to scala in a buildfile, when running buildr's own >>> spec, and so on. >>> >> >> >> Yes, this would be my first choice as well but with the state of RJB and >> Ant >> integration today, the Scala artifacts need to be placed on the classpath >> during the Buildr bootstrap. So I'm not sure if initializing things >> lazily is an option right now. Maybe Assaf has some tricks for this? >> >> alex >> > ------=_Part_11996_10060940.1215111491723--