Charles Oliver Nutter wrote:
Martin Krauskopf wrote:
Hi,
would it be possible to pre-announce releases few days before the real
release day, so interested folks could try whether their code works
with JRuby. I'm trying to stay up-to-date with trunk, but again, too
late.
(http://jira.codehaus.org/browse/JRUBY-3114)
Pre-announcement would help regressions like the ones related to the
debugger (1.1.3 and 1.1.5 breaks the debugger).
Sorry about that...we do need to be better about pre-announcing the
release, and I've actually thought it might be workthwhile to always do
a short, quick series of RCs before the main release.
Looking at JRUBY-3114, I think you may have been using behavior that was
not correct. There were fixes to require because I discovered regardless
of whether there are other like-named libraries in the load path,
requiring "./foo" always looks for foo in the current directory. Note
the following:
[...]
Please correct me if any of this is wrong :)
Yup, thanks for details. I've played with it and seems that just using:
require 'tracelines'
is ok, since the directory where the requirer resides seems to be
preferred (even if the other gem with the same file is installed).
The problem is rather with the ruby-debug(-base) versioning. That it is
not easy to release hot-fixes (like 0.10.2.1). But that will be
hopefully solved for 0.10.3 and further:
http://rubyforge.org/tracker/?func=detail&atid=7439&aid=22698&group_id=1900
If 0.10.3 is not released soon I'll likely re-release the 0.10.2 with
the fix.
So likely just close that issue.
Thanks,
m.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
