[jruby-dev] [jira] Created: (JRUBY-1477) IO Error requiring certain jars in JRoR

IO Error requiring certain jars in JRoR --- Key: JRUBY-1477 URL: http://jira.codehaus.org/browse/JRUBY-1477 Project: JRuby Issue Type: Bug Components: Java Integration Affects Versions: JRuby

[jruby-dev] Tracing in compiler

Your suggestion in JRUBY-1475 (add a flag at startup) makes sense to me. How feasible would it be to add debugging information as part of a bytecode transformation (either as an additional visitor when it's being created or transforming it in the ClassLoader after the fact)? Pete On 10/25/07, Ch

[jruby-dev] [jira] Created: (JRUBY-1476) jruby.home extraction / jar-complete / content mismatch

jruby.home extraction / jar-complete / content mismatch --- Key: JRUBY-1476 URL: http://jira.codehaus.org/browse/JRUBY-1476 Project: JRuby Issue Type: Improvement Components: Misc

[jruby-dev] [jira] Created: (JRUBY-1475) trunk has broken c-call traces

trunk has broken c-call traces -- Key: JRUBY-1475 URL: http://jira.codehaus.org/browse/JRUBY-1475 Project: JRuby Issue Type: Bug Reporter: Charles Oliver Nutter Assignee: Charles Oliver Nut

[jruby-dev] [jira] Created: (JRUBY-1474) Include java support files in exploded form

Include java support files in exploded form --- Key: JRUBY-1474 URL: http://jira.codehaus.org/browse/JRUBY-1474 Project: JRuby Issue Type: Bug Affects Versions: JRuby 1.0.1 Reporter: To

[jruby-dev] [jira] Created: (JRUBY-1473) Mark implementation-oriented classes and methods in the javasupport with :nodoc:

Mark implementation-oriented classes and methods in the javasupport with :nodoc: Key: JRUBY-1473 URL: http://jira.codehaus.org/browse/JRUBY-1473 Project: JRuby

Re: [jruby-dev] jruby-debug stability, enabled in NetBeans (was Re: [jruby-dev] Obscure test/unit interaction problems)

Peter Brant wrote: We are actually quite close. Barring surprises, I should have the remaining API implemented by this time next week. The only jruby-debug related bug that I'm aware of that's still in progress is JRUBY-1286. Unless you're already working on it, I'll add tracing support to the

[jruby-dev] MountainWest RubyConf 2008

MountainWest RubyConf 2008 is scheduled for March 28 and 29, 2008. It will be in Salt Lake City, at the same great venue we had last year, and it is again our intent to record and make available all the talks under a Creative Commons, Share-Alike license -- you can see last year's talks here:

Re: [jruby-dev] jruby-debug stability, enabled in NetBeans (was Re: [jruby-dev] Obscure test/unit interaction problems)

We are actually quite close. Barring surprises, I should have the remaining API implemented by this time next week. The only jruby-debug related bug that I'm aware of that's still in progress is JRUBY-1286. Unless you're already working on it, I'll add tracing support to the compiler after that

Re: [jruby-dev] jruby-debug stability, enabled in NetBeans (was Re: [jruby-dev] Obscure test/unit interaction problems)

Peter Brant wrote: As it turns out, the only one in the weeds was me. After the two aformentioned bug fixes, it was working correctly. I hadn't been following this thread, but wow, sounds like we're really close. Got anything else for JRuby core? - Charlie -

Re: [jruby-dev] "stack level too deep" error when

Thanks for telling :-) On 10/25/07, Charles Oliver Nutter <[EMAIL PROTECTED]> wrote: > > XiaoLiang Liu wrote: > > hi, > > > > I met a strange problem that when I ran "jruby rails abc" in > > $JRUBY_HOME/bin directory, it will get the "stack level too deep" error, > > as the following. But if I ra

Re: [jruby-dev] jruby-debug stability, enabled in NetBeans (was Re: [jruby-dev] Obscure test/unit interaction problems)

As it turns out, the only one in the weeds was me. After the two aformentioned bug fixes, it was working correctly. Pete On 10/24/07, Peter Brant <[EMAIL PROTECTED]> wrote: > > Unfortunately, we still go off into the weeds (although different > weeds now) when stepping over Car.find(). I'll con

[jruby-dev] [jira] Created: (JRUBY-1472) Yaml problem creating single instance for multiple identical objects

Yaml problem creating single instance for multiple identical objects Key: JRUBY-1472 URL: http://jira.codehaus.org/browse/JRUBY-1472 Project: JRuby Issue Type: Bug

[jruby-dev] [jira] Created: (JRUBY-1471) YAML dumping or loading is mucking up object IDs

YAML dumping or loading is mucking up object IDs Key: JRUBY-1471 URL: http://jira.codehaus.org/browse/JRUBY-1471 Project: JRuby Issue Type: Bug Components: Core Classes/Modules A

Re: [jruby-dev] "stack level too deep" error when

XiaoLiang Liu wrote: hi, I met a strange problem that when I ran "jruby rails abc" in $JRUBY_HOME/bin directory, it will get the "stack level too deep" error, as the following. But if I ran the same command in another directory, it will be ok. Does anyone know the reason? Thanks a lot. I

Re: [jruby-dev] Setting up the sandbox

Niels Bech Nielsen wrote: Hi, Charles asked for people to chip in, and I had plenty of time, and thought I might be useful (or useless, whichever). As unprecedented with anything, I will probably start from the head of the JIRA list with the unassigned problems, which in this case is the 13

[jruby-dev] "stack level too deep" error when

hi, I met a strange problem that when I ran "jruby rails abc" in $JRUBY_HOME/bin directory, it will get the "stack level too deep" error, as the following. But if I ran the same command in another directory, it will be ok. Does anyone know the reason? Thanks a lot. == bas

[jruby-dev] Setting up the sandbox

Hi, Charles asked for people to chip in, and I had plenty of time, and thought I might be useful (or useless, whichever). As unprecedented with anything, I will probably start from the head of the JIRA list with the unassigned problems, which in this case is the 1382 concurrency issue. Whe