buildr-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Antoine Toulme <anto...@lunar-ocean.com>
Subject Re: Building and testing Buildr plugins for profit
Date Wed, 03 Jun 2009 09:03:32 GMT
Not sure if I tried that at the time, but the best solution for development
and testing is to use braid.
Thanks,

Antoine

On Wed, Jun 3, 2009 at 06:42, Ittay Dror <ittay.dror@gmail.com> wrote:

>
>
>
> Antoine Toulme wrote:
> >
> > Hi,
> >
> > while it's still fresh, I'd like to share the problems we encountered to
> > build a plugin with Buildr.
> >
> > As you may know, Buildr is packaged as an application, so doing a require
> > "buildr" brings quite a few things.
> >
> > In our case, we wanted to build a spec that was pretty much a copy/paste
> > of
> > javac.
> >
> > We tried first by requiring the gem and some of its modules. It turns out
> > that there are a few clever tricks made in spec/spec_helpers.rb that are
> > necessary to send rake tasks properly.
> >
> > In the end, we were able to test by placing buildr4eclipse along with
> > buildr, and required the file explicitely.
> > With that setup, tests are actually running in the buildr/tmp folder :-/.
> > At
> > least we could run the tests.
> >
> > There doesn't seem to be a way to require spec/spec_helpers.rb in the
> gem.
> > The file is present in there though.
> >
> can't you use:
> require 'buildr/../../spec/spec_helpers'
> ?
>
> ittay
>
>
> >
> > I am quite unsure there is a pleasant way to work around those problems.
> > If
> > the Buildr team is interested into helping with supporting testing of
> > plugins further more, I'd be happy to discuss about it.
> >
> > Thanks,
> >
> > Antoine
> >
> > --
> > http://www.lunar-ocean.com/blog
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/Building-and-testing-Buildr-plugins-for-profit-tp21292871p23845265.html
> Sent from the Buildr - User mailing list archive at Nabble.com.
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message