What's the best way to go about this?
We can swap from depending on JRuby stable to trunk just by changing the
pom, however I don't know of a nice way of dealing with incompatible
APIs between versions without separate branches or using reflection.
Cheers,
Robert
Thomas E Enebo wrote:
I think we need a way to build against trunk and stable added to
goldspikes build system as well.
-Tom
On 7/19/07, Charles Oliver Nutter <[EMAIL PROTECTED]> wrote:
Thomas E Enebo wrote:
I changed the names of Ruby.evalScript on trunk last week to:
Ruby.evalScriptlet(String)
Ruby.evalFile(Reader, String)
Before these were both:
Ruby.evalScript(String)
Ruby.evalScript(Reader, String)
I was going to update this in goldspike, but the build system needs
multiple changes to run against trunk and I did not know exactly what
I needed to change to make sure things are working...
I mentioned this on Raphaël's post, but I'll mention it again...
There will be a 1.0.1 release without the API changes soon, so it might
be best to have a stable GoldSpike release based on that. Incompatible
API changes will remain on trunk to target 1.1 and we'll make a better
effort to merge compatibility and perf changes to the 1.0 branch from
now on.
- Charlie
_______________________________________________
Jruby-extras-devel mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/jruby-extras-devel
_______________________________________________
Jruby-extras-devel mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/jruby-extras-devel
