You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@buildr.apache.org by Alex Boisvert <bo...@intalio.com> on 2008/05/24 18:06:08 UTC

Tip of the week

So you checked out the Buildr source and you've hacked something pretty cool
or added some debug statements to track down your build issue...  so now how
do you test with this custom Buildr source?

Simple!

ruby -I/path/to/your/buildr/lib /path/to/your/buildr/bin/buildr

In the past I've used a combination of "rake -f Buildfile" and placing
something like "$LOAD_PATH.unshift "path/to/my/buildr/lib/" at the top of my
Buildfiles but that didn't work so well...  so I thought I'd share this
little trick that Assaf gave me earlier this week.

cheers,
alex

Re: Tip of the week

Posted by Alexis Midon <al...@gmail.com>.
thank you, doing 'rake install' every time was a pain :)

On Sat, May 24, 2008 at 9:06 AM, Alex Boisvert <bo...@intalio.com> wrote:

> So you checked out the Buildr source and you've hacked something pretty
> cool
> or added some debug statements to track down your build issue...  so now
> how
> do you test with this custom Buildr source?
>
> Simple!
>
> ruby -I/path/to/your/buildr/lib /path/to/your/buildr/bin/buildr
>
> In the past I've used a combination of "rake -f Buildfile" and placing
> something like "$LOAD_PATH.unshift "path/to/my/buildr/lib/" at the top of
> my
> Buildfiles but that didn't work so well...  so I thought I'd share this
> little trick that Assaf gave me earlier this week.
>
> cheers,
> alex
>