Well, there's a couple options here if we decide to integrate merb- cucumber.
1) It could be embedded into merb-gen by default so all someone has to do is run "merb-gen cucumber" to get all the files they need. 2) merb-gen app could just generate the features/, cucumber.yml, and lib/tasks/cucumber.rake to have a working cucumber install by default. I think option 2 would still be pretty non-intrusive. Someone could easily ignore it as it would only run on "rake cucumber". Or they could clear it out easily by running "merb-gen cucumber -d". On Oct 10, 2009, at 4:58 PM, Matt Aimonetti wrote: > I don't think that it should be generated by default for any new > merb app. > > - Matt > > On Sat, Oct 10, 2009 at 1:54 PM, Jacques Crocker > <[email protected]> wrote: > > Cucumber 0.4 just came out and broke anyone using merb_cucumber. A > working version of this library was already 3 times removed (david- > >roman->pk). Seems much too complicated for something as cool and > popular as Cucumber which I'm guessing most merbists are going to be > pretty keen on getting working. > > I've got merb_cucumber working with the latest version and with Merb > 1.1. I'd like to propose moving it into the main merb project as merb- > cucumber, and generating it by default on merb-gen app. > > Any opinions? > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "merb" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/merb?hl=en -~----------~----~----~----~------~----~------~--~---
