I think none of us is using rails 3.1 due to incompatibility of
activerecord-jdbc-adapter.
Isn’t it?
On Sun, Sep 11, 2011 at 10:50 AM, Mauro [email protected] wrote:
I think none of us is using rails 3.1 due to incompatibility of
activerecord-jdbc-adapter.
Isn’t it?
I think none of us is going to read any email from you if you keep
stating such sentences.
Isn’t it ?
Please share how you use activerecord-jdbc-adapter at least beofe
making such statements.
–
Christian
On 11 September 2011 13:00, Christian MICHON
[email protected] wrote:
On Sun, Sep 11, 2011 at 10:50 AM, Mauro [email protected] wrote:
I think none of us is using rails 3.1 due to incompatibility of
activerecord-jdbc-adapter.
Isn’t it?I think none of us is going to read any email from you if you keep
stating such sentences.
On Sun, Sep 11, 2011 at 8:29 PM, Mauro [email protected] wrote:
then why don’t you stay in the same thread ?
–
Christian
On 12 September 2011 09:11, Christian MICHON
[email protected] wrote:
then why don’t you stay in the same thread ?
Have you some problems?
On Sep 12, 2011, at 8:11, Christian MICHON [email protected]
wrote:
then why don’t you stay in the same thread ?
Perhaps he saw it after posting here? If the only answers I got after
posting a friendly email was the sort you provide, then I would
definitely start looking elsewhere.
Aslak
On Mon, Sep 12, 2011 at 9:23 AM, Aslak Hellesy
[email protected] wrote:
I think none of us is going to read any email from you if you keep
Aslak
No Aslak: he started both threads.
You may have missed the point I was trying to make implicitely. Let me
be more explicit.
If you look carefully at most posts from Mauro, they consist mostly of
negative feedbacks. I just wish they could look more like bug reports
(though jira should be used instead) instead of stating pseudo thruths
like <<I think none of us is using rails 3.1 due to incompatibility of
activerecord-jdbc-adapter>>.
–
Christian
On Mon, Sep 12, 2011 at 9:26 AM, Mauro [email protected] wrote:
stating such sentences.
then why don’t you stay in the same thread ?
Have you some problems?
I have no problem. But since you started both threads, I would expect
you to complete the 1st thread, instead of starting a new one with
such statement.
You cannot expect people to read this new thread and understand root
causes without proper clues.
Starting new threads just to vent your frustration (let me reming you
this sentence of yours: << If the migrations don’t work I can’t work
>> ) will get this mailing list to nowhere. I take for example
another parallel thread where you complain about jdbc but your
database.yml is not related to jdbc.
When things do not work immediately out of the box, then maybe a
little work on the side done by you could help you find a fix (at
least this is what I would try to do).
I’ve already mentioned in the past your ‘negative’ attitude to change.
Here: Jruby with ruby1.9 - JRuby - Ruby-Forum.
You apologised then (Jruby with ruby1.9 - JRuby - Ruby-Forum)
but I believe you’ve not changed your manners.
I hope now that Aslak understands more my reaction.
–
Christian
On Mon, Sep 12, 2011 at 9:46 AM, Mauro [email protected] wrote:
I want to know if there someone that use jruby-1.6.4 in 1.9 mode, with
jdbcpostgresql, using the last versione of activerecord-jdbc-adapter
gem and noticed no problems.
I am not English either 
You need to send the right database.yml.
Unless something changed drastically in rails3, at least in rails2
your database.yml should look like this (I am using h2, not
postgresql):
development:
adapter: jdbc
driver: org.h2.Driver
url: jdbc:h2:development
Even in your case, I would expect to see “adapter: jdbcpostgresql”,
but it’s not in the configuration you sent in a parallel thread.
–
Christian
On 12 September 2011 09:50, Christian MICHON
[email protected] wrote:
I can’t explain very well the problems 'cause english is not my mother
language.
your database.yml should look like this (I am using h2, not
postgresql):development:
adapter: jdbc
driver: org.h2.Driver
url: jdbc:h2:developmentEven in your case, I would expect to see “adapter: jdbcpostgresql”,
but it’s not in the configuration you sent in a parallel thread.
Yes but I’ve tried to change the adapter from postgres to
jdbcpostgresql, I’ve run rails c the Shop.all and it works, then
Shop.find(…) and it works, then Shop.count
and…Java::JavaLang::NullPointerException.
So nothing change.
Sorry for the noise, I’m not an expert developer so I can’t help to
fix the problems.
On 12 September 2011 09:40, Christian MICHON
[email protected] wrote:
I have no problem. But since you started both threads, I would expect
you to complete the 1st thread, instead of starting a new one with
such statement.You cannot expect people to read this new thread and understand root
causes without proper clues.
I can’t explain very well the problems 'cause english is not my mother
language.
I want to know if there someone that use jruby-1.6.4 in 1.9 mode, with
jdbcpostgresql, using the last versione of activerecord-jdbc-adapter
gem and noticed no problems.
On Mon, Sep 12, 2011 at 9:54 AM, Mauro [email protected] wrote:
Unless something changed drastically in rails3, at least in rails2
Yes but I’ve tried to change the adapter from postgres to
jdbcpostgresql, I’ve run rails c the Shop.all and it works, then
Shop.find(…) and it works, then Shop.count
and…Java::JavaLang::NullPointerException.
So nothing change.
The configuration is different.
Java::JavaLang::NullPointerException is just a piece of the puzzle.
Could you send the full trace to the list please?
Sorry for the noise, I’m not an expert developer so I can’t help to
fix the problems.
You can help by reporting them fully. I’m not a jruby developper
either, but I use jruby with many projects. If I can see a full trace
of a problem I faced and I changed my code to make it pass, I can
share my fix with you.
If I only see negative statements (regardless of you not being
English), I will not feel like trying to find a fix.
–
Christian
On 12 September 2011 10:00, Christian MICHON
[email protected] wrote:
You can help by reporting them fully. I’m not a jruby developper
either, but I use jruby with many projects. If I can see a full trace
of a problem I faced and I changed my code to make it pass, I can
share my fix with you.If I only see negative statements (regardless of you not being
English), I will not feel like trying to find a fix.
I report the full trace when I do Shop.count.
I want tell that I’m using activerecord-jdbc-adapter from github
master branch because with the last version of the gem I can’t do
migrations, if you want I can report the full trace of the failed
migrations too.
database.yml:
development:
adapter: jdbcpostgresql
encoding: unicode
database: attivita_produttive_development
pool: 5
username: xxx
password: yyy
host: localhost
port: 5432
rails c
Loading development environment (Rails 3.1.0)
/home/mauro/jruby/lib/ruby/1.9/irb/input-method.rb:108 warning:
Ignoring internal encoding UTF-8: it is identical to external encoding
UTF-8
/home/mauro/jruby/lib/ruby/1.9/irb/input-method.rb:109 warning:
Ignoring internal encoding UTF-8: it is identical to external encoding
UTF-8
irb(main):001:0> Shop.count
Java::JavaLang::NullPointerException:
from org.jruby.RubyProc.call19(RubyProc.java:248)
from
org.jruby.RubyProc$i$0$0$call19.call(RubyProc$i$0$0$call19.gen:65535)
from
org.jruby.internal.runtime.methods.DynamicMethod.call(DynamicMethod.java:211)
from
org.jruby.internal.runtime.methods.DynamicMethod.call(DynamicMethod.java:207)
from
org.jruby.runtime.callsite.CachingCallSite.cacheAndCall(CachingCallSite.java:312)
from
org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:169)
from
org.jruby.ast.CallOneArgNode.interpret(CallOneArgNode.java:57)
from org.jruby.ast.NewlineNode.interpret(NewlineNode.java:104)
from org.jruby.ast.BlockNode.interpret(BlockNode.java:71)
from
org.jruby.evaluator.ASTInterpreter.INTERPRET_METHOD(ASTInterpreter.java:75)
from
org.jruby.internal.runtime.methods.InterpretedMethod.call(InterpretedMethod.java:190)
from
org.jruby.internal.runtime.methods.DefaultMethod.call(DefaultMethod.java:179)
from
org.jruby.runtime.callsite.CachingCallSite.cacheAndCall(CachingCallSite.java:312)
from
org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:169)
from org.jruby.ast.FCallOneArgNode.interpret(FCallOneArgNode.java:36)
from org.jruby.ast.NewlineNode.interpret(NewlineNode.java:104)
… 467 levels…
from
org.jruby.internal.runtime.methods.AliasMethod.call(AliasMethod.java:61)
from
org.jruby.internal.runtime.methods.AliasMethod.call(AliasMethod.java:61)
from
org.jruby.runtime.callsite.CachingCallSite.cacheAndCall(CachingCallSite.java:312)
from
org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:169)
from script.rails.file(script/rails:6)
from script.rails.load(script/rails)
from org.jruby.Ruby.runScript(Ruby.java:679)
from org.jruby.Ruby.runScript(Ruby.java:672)
from org.jruby.Ruby.runNormally(Ruby.java:579)
from org.jruby.Ruby.runFromMain(Ruby.java:428)
from org.jruby.Main.doRunFromMain(Main.java:278)
from org.jruby.Main.internalRun(Main.java:198)
from org.jruby.Main.run(Main.java:164)
from org.jruby.Main.run(Main.java:148)
from
org.jruby.util.ShellLauncher$ScriptThreadProcess.run(ShellLauncher.java:140)
from java.lang.Thread.run(Thread.java:679)irb(main):002:0>
Shop.count
On Mon, Sep 12, 2011 at 10:07 AM, Mauro [email protected] wrote:
I report the full trace when I do Shop.count.
username: xxx
/home/mauro/jruby/lib/ruby/1.9/irb/input-method.rb:109 warning:
from
org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:169)
… 467 levels…
from org.jruby.Main.doRunFromMain(Main.java:278)
from org.jruby.Main.internalRun(Main.java:198)
from org.jruby.Main.run(Main.java:164)
from org.jruby.Main.run(Main.java:148)
from
org.jruby.util.ShellLauncher$ScriptThreadProcess.run(ShellLauncher.java:140)
from java.lang.Thread.run(Thread.java:679)irb(main):002:0>Shop.count
Now that’s what I call a bug report
Could you please also share how you created the model ‘Shop’ ? This
would help recreating the bug.
Thanks.
–
Christian
On 12 September 2011 10:15, Christian MICHON
[email protected] wrote:
Now that’s what I call a bug report
Oh finally
Could you please also share how you created the model ‘Shop’ ? This
would help recreating the bug.
rails g scaffold shop name:string ssn:string nationality:string
address:string street_number:string website:string district:integer
sector:string square_meters:decimal duaap:integer description:string
state:string notes:text.
I report the Gemfile too:
source ‘http://rubygems.org’
gem ‘rails’
gem ‘annotate’
gem ‘normalize_attributes’
gem ‘haml-rails’
gem ‘devise_ldap_authenticatable’
gem ‘meta_search’
gem ‘simple_form’
gem ‘fastercsv’
gem ‘inherited_resources’
gem ‘app_config’
gem ‘simple-navigation’
gem ‘thin’
gem ‘kaminari’
gem ‘activerecord-jdbc-adapter’, :git =>
‘git://github.com/jruby/activerecord-jdbc-adapter.git’
gem ‘activerecord-jdbcpostgresql-adapter’
gem ‘jruby-openssl’
gem ‘json’
group :assets do
gem ‘sass-rails’
gem ‘coffee-rails’
gem ‘uglifier’
gem ‘compass’, :git =>
‘GitHub - Compass/compass: Compass is no longer actively maintained. Compass is a Stylesheet Authoring Environment that makes your website design simpler to implement and easier to maintain.’, :branch => ‘rails31’
end
gem ‘jquery-rails’
platforms :jruby do
group :assets do
gem ‘therubyrhino’
end
end
group :test do
Pretty printed test output
gem ‘turn’, :require => false
gem ‘rspec-rails’
gem ‘cucumber-rails’
gem ‘capybara’
gem ‘launchy’
gem ‘autotest-rails’
gem ‘autotest-notification’
gem ‘database_cleaner’
gem ‘spork’, ‘~> 0.9.0.rc’
gem ‘machinist’, ‘>= 2.0.0.beta’
end
group :development do
gem ‘hpricot’
gem ‘ruby_parser’
gem ‘warbler’ if defined?(JRUBY_VERSION)
end
On Mon, Sep 12, 2011 at 10:22 AM, Mauro [email protected] wrote:
address:string street_number:string website:string district:integer
sector:string square_meters:decimal duaap:integer description:string
state:string notes:text.
OK.
I tried with h2 database as I do not have postgresql. I tried rails
3.1 with activerecord-jdbc-adapter/master in 1.8 mode: it works fine.
I later tried with --1.9 mode (from the start, project creation
included): it fails at the ‘rake db:migrate’.
Here’s my trace:
rake --trace db:migrate
** Invoke db:migrate (first_time)
** Invoke environment (first_time)
** Execute environment
** Invoke db:load_config (first_time)
** Invoke rails_env (first_time)
** Execute rails_env
** Execute db:load_config
** Execute db:migrate
== CreateShops: migrating
– create_table(:shops)
→ 0.0940s
→ 0 rows
== CreateShops: migrated (0.0940s)
rake aborted!
An error has occurred, all later migrations canceled:
TypeError: can’t convert nil into Integer: INSERT INTO
schema_migrations (version) VALUES (‘20110912090004’)
org/jruby/RubyKernel.java:444:in Integer' file:C:/jruby/bin/r3.jar!/gems/activerecord-jdbc-adapter-1.1.3/lib/arjdbc/hsqldb/adapter.rb:137:in last_insert_id’
file:C:/jruby/bin/r3.jar!/gems/activerecord-jdbc-adapter-1.1.3/lib/arjdbc/hsqldb/adapter.rb:142:in
_execute' file:C:/jruby/bin/r3.jar!/gems/activerecord-jdbc-adapter-1.1.3/lib/arjdbc/jdbc/adapter.rb:208:in execute’
file:C:/jruby/bin/r3.jar!/gems/activerecord-3.1.0/lib/active_record/connection_adapters/abstract_adapter.rb:244:in
log' file:C:/jruby/bin/r3.jar!/gems/activesupport-3.1.0/lib/active_support/notifications/instrumenter.rb:21:in instrument’
file:C:/jruby/bin/r3.jar!/gems/activerecord-3.1.0/lib/active_record/connection_adapters/abstract_adapter.rb:239:in
log' file:C:/jruby/bin/r3.jar!/gems/activerecord-jdbc-adapter-1.1.3/lib/arjdbc/jdbc/adapter.rb:208:in execute’
file:C:/jruby/bin/r3.jar!/gems/activerecord-jdbc-adapter-1.1.3/lib/arjdbc/jdbc/adapter.rb:263:in
exec_query' file:C:/jruby/bin/r3.jar!/gems/activerecord-jdbc-adapter-1.1.3/lib/arjdbc/jdbc/adapter.rb:270:in exec_insert’
file:C:/jruby/bin/r3.jar!/gems/activerecord-3.1.0/lib/active_record/connection_adapters/abstract/database_statements.rb:90:in
insert' file:C:/jruby/bin/r3.jar!/gems/activerecord-3.1.0/lib/active_record/connection_adapters/abstract/query_cache.rb:19:in insert’
file:C:/jruby/bin/r3.jar!/gems/activerecord-3.1.0/lib/active_record/migration.rb:727:in
record_version_state_after_migrating' file:C:/jruby/bin/r3.jar!/gems/activerecord-3.1.0/lib/active_record/migration.rb:688:in migrate’
org/jruby/RubyProc.java:262:in call' file:C:/jruby/bin/r3.jar!/gems/activerecord-3.1.0/lib/active_record/migration.rb:744:in ddl_transaction’
file:C:/jruby/bin/r3.jar!/gems/activerecord-3.1.0/lib/active_record/migration.rb:686:in
migrate' org/jruby/RubyArray.java:1603:in each’
file:C:/jruby/bin/r3.jar!/gems/activerecord-3.1.0/lib/active_record/migration.rb:671:in
migrate' file:C:/jruby/bin/r3.jar!/gems/activerecord-3.1.0/lib/active_record/migration.rb:549:in up’
file:C:/jruby/bin/r3.jar!/gems/activerecord-3.1.0/lib/active_record/migration.rb:530:in
migrate' file:C:/jruby/bin/r3.jar!/gems/activerecord-3.1.0/lib/active_record/railties/databases.rake:161:in (root)’
org/jruby/RubyProc.java:262:in call' file:C:/jruby/bin/r3.jar!/gems/rake-0.9.2/lib/rake/task.rb:205:in execute’
org/jruby/RubyArray.java:1603:in each' file:C:/jruby/bin/r3.jar!/gems/rake-0.9.2/lib/rake/task.rb:200:in execute’
file:C:/jruby/bin/r3.jar!/gems/rake-0.9.2/lib/rake/task.rb:158:in
invoke_with_call_chain' file:/C:/jruby/bin/jruby-complete-1.6.4.jar!/META-INF/jruby.home/lib/ruby/1.9/monitor.rb:201:in mon_synchronize’
file:C:/jruby/bin/r3.jar!/gems/rake-0.9.2/lib/rake/task.rb:151:in
invoke_with_call_chain' file:C:/jruby/bin/r3.jar!/gems/rake-0.9.2/lib/rake/task.rb:144:in invoke’
file:C:/jruby/bin/r3.jar!/gems/rake-0.9.2/lib/rake/application.rb:112:in
invoke_task' file:C:/jruby/bin/r3.jar!/gems/rake-0.9.2/lib/rake/application.rb:90:in top_level’
org/jruby/RubyArray.java:1603:in each' file:C:/jruby/bin/r3.jar!/gems/rake-0.9.2/lib/rake/application.rb:90:in top_level’
file:C:/jruby/bin/r3.jar!/gems/rake-0.9.2/lib/rake/application.rb:129:in
standard_exception_handling' file:C:/jruby/bin/r3.jar!/gems/rake-0.9.2/lib/rake/application.rb:84:in top_level’
file:C:/jruby/bin/r3.jar!/gems/rake-0.9.2/lib/rake/application.rb:62:in
run' file:C:/jruby/bin/r3.jar!/gems/rake-0.9.2/lib/rake/application.rb:129:in standard_exception_handling’
file:C:/jruby/bin/r3.jar!/gems/rake-0.9.2/lib/rake/application.rb:59:in
run' file:C:/jruby/bin/r3.jar!/gems/rake-0.9.2/bin/rake:32:in (root)’
org/jruby/RubyKernel.java:1073:in load' file:C:/jruby/bin/r3.jar!/gems/rake-0.9.2/bin/rake:19:in (root)’
org/jruby/RubyKernel.java:1073:in load' file:/C:/jruby/bin/jruby-complete-1.6.4.jar!/META-INF/jruby.home/bin/rake:12:in rake’
rake:1:in `(root)’
Tasks: TOP => db:migrate
So I’m guessing you created the project in 1.8 mode, made your
migrations, then tried in 1.9 mode.
Because if I do that, and I call rails 3 console in 1.9 mode, I get
this:
Loading development environment (Rails 3.1.0)
irb(main):001:0> Shop.count
Java::JavaLang::NullPointerException:
from org.jruby.RubyProc.call19(RubyProc.java:248)
from
org.jruby.RubyProc$i$0$0$call19.call(RubyProc$i$0$0$call19.gen:65535)
from
org.jruby.internal.runtime.methods.DynamicMethod.call(DynamicMethod.java:211)
from
org.jruby.internal.runtime.methods.DynamicMethod.call(DynamicMethod.java:207)
from
org.jruby.runtime.callsite.CachingCallSite.cacheAndCall(CachingCallSite.java:312)
from
org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:169)
from
org.jruby.ast.CallOneArgNode.interpret(CallOneArgNode.java:57)
from org.jruby.ast.NewlineNode.interpret(NewlineNode.java:104)
from org.jruby.ast.BlockNode.interpret(BlockNode.java:71)
from
org.jruby.evaluator.ASTInterpreter.INTERPRET_METHOD(ASTInterpreter.java:75)
from
org.jruby.internal.runtime.methods.InterpretedMethod.call(InterpretedMethod.java:190)
from
org.jruby.internal.runtime.methods.DefaultMethod.call(DefaultMethod.java:179)
from
org.jruby.runtime.callsite.CachingCallSite.cacheAndCall(CachingCallSite.java:312)
from
org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:169)
from
org.jruby.ast.FCallOneArgNode.interpret(FCallOneArgNode.java:36)
from org.jruby.ast.NewlineNode.interpret(NewlineNode.java:104)
… 451 levels…
from
org.jruby.internal.runtime.methods.JavaMethod$JavaMethodOneOrNBlock.call(JavaMethod.java:319)
from
org.jruby.internal.runtime.methods.AliasMethod.call(AliasMethod.java:61)
from
org.jruby.internal.runtime.methods.AliasMethod.call(AliasMethod.java:61)
from
org.jruby.runtime.callsite.CachingCallSite.cacheAndCall(CachingCallSite.java:312)
from
org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:169)
from script.rails.file(script/rails:6)
from script.rails.load(script/rails)
from org.jruby.Ruby.runScript(Ruby.java:679)
from org.jruby.Ruby.runScript(Ruby.java:672)
from org.jruby.Ruby.runNormally(Ruby.java:579)
from org.jruby.Ruby.runFromMain(Ruby.java:428)
from org.jruby.Main.doRunFromMain(Main.java:278)
from org.jruby.Main.internalRun(Main.java:198)
from org.jruby.Main.run(Main.java:164)
from org.jruby.Main.run(Main.java:148)
from org.jruby.Main.main(Main.java:128)irb(main):002:0>
So it’s not a real bug: you did not use 1.9 mode all the way.
The real bug is that in 1.9 mode, you cannot get past db migrations.
This is the real step which needs fixing.
Maybe it’s activerecord, maybe it’s activerecord-jdbc-adapter, maybe
it’s jruby.
Here are the command lines to make this happen:
rails new foo
cd foo
REM modify database.yml and gemfile accordingly
jruby script/rails g scaffold shop name:string ssn:string
nationality:string address:string street_number:string website:string
district:integer sector:string square_meters:decimal duaap:integer
description:string state:string notes:text
rake db:migrate
jruby script/rails c
–
Christian
On 12 September 2011 11:36, Mauro [email protected] wrote:
On 12 September 2011 11:13, Christian MICHON [email protected] wrote:
So I’m guessing you created the project in 1.8 mode, made your
migrations, then tried in 1.9 mode.Thanks for your patience, I try to recreate the app starting in 1.9 mode.
But I’m not lucky, now it seems there is a problem with rubygem:
bundle install
ArgumentError: undefined class/module YAML::Syck::DefaultKey
As I thought is not a mix problem.
I’ve created a new app in jruby mode.
rails c
irb(main):004:0> Shop.all
Shop Load (1.0ms) SELECT “shops”.* FROM “shops”
=> []
irb(main):005:0> Shop.count
Java::JavaLang::NullPointerException:
from org.jruby.RubyProc.call19(RubyProc.java:248)
from
org.jruby.RubyProc$i$0$0$call19.call(RubyProc$i$0$0$call19.gen:65535)
from
org.jruby.internal.runtime.methods.DynamicMethod.call(DynamicMethod.java:211)
from
org.jruby.internal.runtime.methods.DynamicMethod.call(DynamicMethod.java:207)
from
org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:167)
from
org.jruby.ast.CallOneArgNode.interpret(CallOneArgNode.java:57)
from org.jruby.ast.NewlineNode.interpret(NewlineNode.java:104)
from org.jruby.ast.BlockNode.interpret(BlockNode.java:71)
from
org.jruby.evaluator.ASTInterpreter.INTERPRET_METHOD(ASTInterpreter.java:75)
from
org.jruby.internal.runtime.methods.InterpretedMethod.call(InterpretedMethod.java:190)
from
org.jruby.internal.runtime.methods.DefaultMethod.call(DefaultMethod.java:179)
from
org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:167)
from org.jruby.ast.FCallOneArgNode.interpret(FCallOneArgNode.java:36)
from org.jruby.ast.NewlineNode.interpret(NewlineNode.java:104)
from
org.jruby.evaluator.ASTInterpreter.INTERPRET_METHOD(ASTInterpreter.java:75)
from
org.jruby.internal.runtime.methods.InterpretedMethod.call(InterpretedMethod.java:212)
… 435 levels…
from
org.jruby.internal.runtime.methods.AliasMethod.call(AliasMethod.java:61)
from
org.jruby.internal.runtime.methods.AliasMethod.call(AliasMethod.java:61)
from
org.jruby.runtime.callsite.CachingCallSite.cacheAndCall(CachingCallSite.java:312)
from
org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:169)
from script.rails.file(script/rails:6)
from script.rails.load(script/rails)
from org.jruby.Ruby.runScript(Ruby.java:679)
from org.jruby.Ruby.runScript(Ruby.java:672)
from org.jruby.Ruby.runNormally(Ruby.java:579)
from org.jruby.Ruby.runFromMain(Ruby.java:428)
from org.jruby.Main.doRunFromMain(Main.java:278)
from org.jruby.Main.internalRun(Main.java:198)
from org.jruby.Main.run(Main.java:164)
from org.jruby.Main.run(Main.java:148)
from
org.jruby.util.ShellLauncher$ScriptThreadProcess.run(ShellLauncher.java:140)
from java.lang.Thread.run(Thread.java:679)irb(main):006:0>
On 12 September 2011 11:13, Christian MICHON
[email protected] wrote:
So I’m guessing you created the project in 1.8 mode, made your
migrations, then tried in 1.9 mode.
Thanks for your patience, I try to recreate the app starting in 1.9
mode.
But I’m not lucky, now it seems there is a problem with rubygem:
bundle install
ArgumentError: undefined class/module YAML::Syck::DefaultKey
As I thought is not a mix problem.
I’ve created a new app in jruby mode.
I want to say jruby 1.9 mode.
On Mon, Sep 12, 2011 at 12:46 PM, Mauro [email protected] wrote:
from org.jruby.RubyProc.call19(RubyProc.java:248)
from
org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:167)
from script.rails.load(script/rails)
To unsubscribe from this list, please visit:
Have you done this on a fresh/empty database ? Did you run the
migrations again in jruby 1.9 mode ?
–
Christian