buildr-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Assaf Arkin <ar...@intalio.com>
Subject Re: Testing out Buildr 1.3.2 gem install
Date Thu, 03 Jul 2008 18:46:03 GMT
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" <boisvert@intalio.com>  
wrote:

> On Wed, Jul 2, 2008 at 10:40 PM, lacton <lacton@users.sourceforge.net>
> 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

Mime
View raw message