Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"unknown method name `map'" during resolve #3

Closed
rsutphin opened this issue May 26, 2010 · 3 comments
Closed

"unknown method name `map'" during resolve #3

rsutphin opened this issue May 26, 2010 · 3 comments

Comments

@rsutphin
Copy link

With buildr 1.3.5 and ivy4r 0.10.5, I'm seeing an exception whenever I do ivy:resolve. I put a minimal sample project as a gist. The trace output for the exception is there, but here's the short version:

[ivy_resolve] :: resolution report :: resolve 128ms :: artifacts dl 4ms
---------------------------------------------------------------------
|                  |            modules            ||   artifacts   |
|       conf       | number| search|dwnlded|evicted|| number|dwnlded|
---------------------------------------------------------------------
|      compile     |   1   |   0   |   0   |   0   ||   2   |   0   |
---------------------------------------------------------------------
Buildr aborted!
Fail: unknown method name `map'
@rsutphin
Copy link
Author

I forgot to mention my environment: MRI 1.8.6-p383, Antwrap 1.7.0 (which is the only version that buildr 1.3.5 will work with).

@rsutphin
Copy link
Author

Further testing reveals that this problem does not occur on JRuby 1.4.0, so that's a workaround.

It would be nice if ivy4r worked on MRI too but failing that it would be good to have a warning high in the README about it being jruby-only.

@klaas1979
Copy link
Owner

I tested around with this. Right now ivy4r only supports JRuby but it was easy to fix. The next release will have a fix for this. It should be release 0.11.x. I try to fix some of the other issues and make one release for it. As you said: use JRuby till the next release is out

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants