doesn't appear to be 1.9 compatible about braid HOT 12 CLOSED

I totally concur. Same error here with rails & ruby latest.

I was hoping a lot about braid, but was sadly disappointed. Maybe I'll give it a try in a while...

from braid.

this project appears to be unmaintained. please refile this bug over here: https://github.com/ttilley/braid

...not that I'm able to take over maintenance, but since I've been in the code to fix it for jruby recently, and have it somewhat fresh in my mind, then I might as well work on it, right?

from braid.

By the way, what is the exact difference between braid and git submodule ?

from braid.

Hop on over to the open source "Pro Git" book and read the section on submodules... Specifically, skip down to the end and read "issues with submodules": http://progit.org/book/ch6-6.html

What braid does is get around these issues by using a subtree merge, and making it really simple to do so:
http://progit.org/book/ch6-7.html

Above and beyond the helper functionality, braid allows you to use svn remotes without needing to care that they're being accessed via git-svn, push local changes to the subtree remote handling all of the complexities for you without polluting the history of the remote, easily decide whether to interleave history with the remote or squash pulls into singular commits (without, btw, interfering with your ability to push changes back to said remote).

from braid.

Hey ttiley !

1. your explanation makes perfect sense and desserve to be placed in braid front page
2. I cannot file bugs in your fork. Maybe you need to enable this feature ?
   Best regards.

from braid.

I still have this problem (when I call braid update). I'm using ttilley's fork (v0.7). ttilley, do you have an idea on how to fix it? For the time being, I'm using rvm to go back to ruby 1.8, call braid update then come back to ruby 1.9.2. Not the most streamlined process...

F, [2011-06-23T08:27:03.433157 #4893] FATAL -- : wrong number of arguments (1 for 0) (ArgumentError)
/Users/renajohn/.rvm/gems/ruby-1.9.2-p180/gems/main-4.4.0/lib/main/parameter.rb:574:in `block in fattr_block_for'
/Users/renajohn/.rvm/gems/ruby-1.9.2-p180/gems/fattr-2.2.0/lib/fattr.rb:90:in `instance_eval'
/Users/renajohn/.rvm/gems/ruby-1.9.2-p180/gems/fattr-2.2.0/lib/fattr.rb:90:in `call'
/Users/renajohn/.rvm/gems/ruby-1.9.2-p180/gems/fattr-2.2.0/lib/fattr.rb:90:in `block (2 levels) in fattrs'
/Users/renajohn/.rvm/gems/ruby-1.9.2-p180/gems/fattr-2.2.0/lib/fattr.rb:139:in `call'
/Users/renajohn/.rvm/gems/ruby-1.9.2-p180/gems/fattr-2.2.0/lib/fattr.rb:139:in `block (3 levels) in fattrs'
(eval):4:in `verbose'
/Users/renajohn/.rvm/gems/ruby-1.9.2-p180/gems/braid-0.7.0/bin/braid:81:in `block (3 levels) in <top (required)>'
/Users/renajohn/.rvm/gems/ruby-1.9.2-p180/gems/main-4.4.0/lib/main/program/class_methods.rb:155:in `block in run'
/Users/renajohn/.rvm/gems/ruby-1.9.2-p180/gems/main-4.4.0/lib/main/program/class_methods.rb:144:in `catch'
/Users/renajohn/.rvm/gems/ruby-1.9.2-p180/gems/main-4.4.0/lib/main/program/class_methods.rb:144:in `run'
/Users/renajohn/.rvm/gems/ruby-1.9.2-p180/gems/main-4.4.0/lib/main/factories.rb:18:in `run'
/Users/renajohn/.rvm/gems/ruby-1.9.2-p180/gems/main-4.4.0/lib/main/factories.rb:25:in `Main'
/Users/renajohn/.rvm/gems/ruby-1.9.2-p180/gems/braid-0.7.0/bin/braid:13:in `<top (required)>'
/Users/renajohn/.rvm/gems/ruby-1.9.2-p180/bin/braid:19:in `load'
/Users/renajohn/.rvm/gems/ruby-1.9.2-p180/bin/braid:19:in `<main>'

PS: can you activate the Issues section in your fork?

Best regards

from braid.

As for me, I've given up about braid because of this.

from braid.

the perils of depending on an unmaintained project. :(

replace your install of main with: https://github.com/oliamb/main.git

that should, in theory, fix braid for 1.9.x. the downside being... how does one depend on a non-existant version of an unmaintained gem?

I'd love to nuke main and simplify braid significantly, but I don't have that kind of spare time atm. -_-

from braid.

I candidly thought the problem was in Braid, my bad!

Following ttilley comment, I went to main githup page and find a simple fix on the following issue.

You just need to change line 574 of lib/main/parameter.rb from:
lambda{ block.call self.param[name] }
to:
lambda{|*args| block.call self.param[name] }

braid update finally works now!

Thanks!

from braid.

...I guess I could duck punch it until I have time to refactor things a bit.

Aside: I have enabled the issue tracker on ttilley/braid (sorry about that!)

from braid.

I've convinced the 'main' author to release a new version. Braid is now Ruby 1.9 compatible! This bug can now be closed.

from braid.

glorious. :)

from braid.