Raphaël Valyi wrote: > Hi, > > short summary of what I did to try out the last Goldspike on JRuby > head and discovered that the memory leak was gone: > > get the Goldspike Rails plugin from head using SVN: > script/plugin install > svn://rubyforge.org/var/svn/jruby-extras/trunk/rails-integration/plugins/goldspike > get the Rails-integration from SVN head from JRuby-extras > get JRuby from head using SVN > build JRuby with jar-complete task > > you have to patch Goldspike so it can run with last JRuby (rev 4047 for me): > - in RailsServlet: change runtime.evalScript into runtime.evalScriptlet. > - also drop the ASTSerializerMain class as it's not compilling and not > used anymore
FYI, we're going to push out a 1.0.1 release soon that has most of the fixes on trunk without the API changes. Ola and Nick are coordinating on that. Going forward, we'll make a best effort to get compatibility and minor performance patches merged to 1.0 branch while keeping incompatible API and runtime changes only on trunk. > now you won't be able to compile Goldspike cause it's changed to > compile with JRuby head, not the Jruby 1.0 Maven will grab from the > mysterious repository. So basically upgrading/rebuilding GoldSpike to run with current JRuby has solved it for you? > PS: JRuby on Rails will only succed if it keeps things simple and can > scale down just like Rails and Webrick... Yeah, that whole process for upgrading is pretty painful... - Charlie _______________________________________________ Jruby-extras-devel mailing list [email protected] http://rubyforge.org/mailman/listinfo/jruby-extras-devel
