1.1 and above represents the development series of the next major version. You will not see this sort of change in the 1.0 stable branch, but we will not mtaintain backwards compat for things like 'raw' embedding between major versons.
rails-integration will need to deal with these changes and create a build for stable and for trunk (1.1). Raw embedding is something we need to change so that it is not so brittle. One solution to this is to include the JSR223 implementation in our release (and make it work for Java 5). Then people using that will never need change their code again. The second solution (which we will do to support both BSF and JSR223) is to make JavaEmbedUtils a 'raw' API for doing all the things embedders/scripting-APIs need to do. I know this is a little painful, but if you seen the number of methods dangling off of Ruby.java you would not grudge us cleaning some stuff up and not growing it to include a bunch of methods which would propagate confusion. -Tom On 8/18/07, Alexey Verkhovsky <[EMAIL PROTECTED]> wrote: > Hi all, > > If I'm not mistaken, org.jruby.Ruby#evalScript() was renamed to > org.jruby.Ruby#evalScriptlet() in the trunk after 1.0 release. This > breaks rails-integration (and probably not only that). > > Since 1.0 is already out in the wild, changes to the API surface > should probably be handled slowly and cautiously, through deprecation. > > -- > Alexey Verkhovsky > CruiseControl.rb [http://cruisecontrolrb.thoughtworks.com] > RubyWorks [http://rubyworks.thoughtworks.com] > > --------------------------------------------------------------------- > To unsubscribe from this list please visit: > > http://xircles.codehaus.org/manage_email > > -- Blog: http://www.bloglines.com/blog/ThomasEEnebo Email: [EMAIL PROTECTED] , [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
