google-code-export / ruby-activeldap

Automatically exported from code.google.com/p/ruby-activeldap
Other
1 stars 1 forks source link

Does not work with rails 2.3.5. #37

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Start a rails project (rails project && cd project)
2. Add config.gem 'active_ldap' to env/config.rb
3. script/console

What is the expected output? What do you see instead?

I expect console to start.  Instead I get an error like:

"can't activate activesupport (= 2.3.4, runtime) for [], already activated
activesupport-2.3.5 for ["rails-2.3.5"] (Gem::LoadError)
...
from...active_ldap.rb:899

What version of the product are you using? On what operating system?

Latest: active_ldap-1.2.0

Please provide any additional information below.

The call should be for a version >= 2.3.4, not precisely 2.3.4.  Apparent
workaround is to use rails 2.3.4 until the bug is fixed in active_ldap.

Original issue reported on code.google.com by aepstein...@gmail.com on 10 Dec 2009 at 7:21

GoogleCodeExporter commented 9 years ago
The dependencies in the Rakefile need to be changed from 2.3.4, so the gem gets 
built with the right deps. I 
manually changed the deps in the gemspec after installing and it worked.

Original comment by zachw...@gmail.com on 16 Dec 2009 at 5:47

GoogleCodeExporter commented 9 years ago
Thanks for your notification.
I've fixed it in trunk.

Original comment by kou...@gmail.com on 16 Dec 2009 at 11:35

GoogleCodeExporter commented 9 years ago
I suggested making the dependency ">= 2.3.4" so as there are new releases of 
activerecord, forward compatibility is assumed.  Unless this depends on 
deprecated parts of the API it should work with later releases of activerecord 
and not be pinned to a particular release.  Is there any reason it can't be 
something like ">= 2.3.4" so it works or at least tries to work with 2.3.4, 
2.3.5, 2.3.8, etc. and 3.x releases?

Original comment by aepstein...@gmail.com on 24 Jun 2010 at 1:44

GoogleCodeExporter commented 9 years ago
ActiveLdap uses ActiveRecord API deeply. It also includes internal API. We 
can't assume that ActiveLdap can work with several ActiveRecord versions. 
ActiveLdap at least can't work with 3.x releases.

If you want to try other ActiveRecord version, you should modify ActiveLdap at 
your own risk.

Original comment by kou...@gmail.com on 25 Jun 2010 at 11:34