YAML edge cases
---
Key: JRUBY-2658
URL: http://jira.codehaus.org/browse/JRUBY-2658
Project: JRuby
Issue Type: Bug
Components: Miscellaneous
Environment: OS X 10.5 using JDK 1.5 and JRuby's trunk
Re
Stringio#ungetc crashes JRuby in some cases
---
Key: JRUBY-2659
URL: http://jira.codehaus.org/browse/JRUBY-2659
Project: JRuby
Issue Type: Bug
Components: Core Classes/Modules
Affects Ver
More than 30 rubyspec failures for StringIO
---
Key: JRUBY-2660
URL: http://jira.codehaus.org/browse/JRUBY-2660
Project: JRuby
Issue Type: Bug
Components: Core Classes/Modules
Affects Ver
The jar-complete ant target currently renames the ASM classes
(org.objectweb.*), but not classes for Joda Time, JNA, and other external
libs. Is there a reason not to rename the others? For orgs like mine,
which prefer not to modify imported open source libs, it would be helpful if
all external d
Bill Dortch wrote:
The jar-complete ant target currently renames the ASM classes
(org.objectweb.*), but not classes for Joda Time, JNA, and other
external libs. Is there a reason not to rename the others? For orgs
like mine, which prefer not to modify imported open source libs, it
would be h
On 6/14/08, Charles Oliver Nutter <[EMAIL PROTECTED]> wrote:
>
> I don't really see a reason not to, other than that JNA has native libs
> that would not take kindly to package renaming. One thing I *don't* like
> about the renaming is that if I want to use any of those libraries from
> within Ruby
specs hang under Apple Java 5
-
Key: JRUBY-2661
URL: http://jira.codehaus.org/browse/JRUBY-2661
Project: JRuby
Issue Type: Bug
Components: Miscellaneous
Affects Versions: JRuby 1.1.2
Repo
Tag or fix remaining OS X spec failures
---
Key: JRUBY-2662
URL: http://jira.codehaus.org/browse/JRUBY-2662
Project: JRuby
Issue Type: Bug
Components: Miscellaneous
Affects Versions: JRuby 1.
Re: mangled names, ah, you mean *Ruby* Ruby code, not Java Ruby code. But
do you mean for internal libs (site-ruby) or apps? For apps, you can just
include the real jar in the classpath (which is the situation I have, hence
the potential version conflict).
On 6/14/08, Charles Oliver Nutter <[EMA
Bill Dortch wrote:
Re: mangled names, ah, you mean *Ruby* Ruby code, not Java Ruby code.
But do you mean for internal libs (site-ruby) or apps? For apps, you
can just include the real jar in the classpath (which is the situation I
have, hence the potential version conflict).
Yes, I mean rub
Charles Oliver Nutter wrote:
Of course, I don't think we have jarjar culling unused classes either,
which might be useful and which would make piggybacking impossible and
perhaps less desirable in light of potential size reduction.
FYI I just tried turning on unreferenced class culling (using
[PATCH] fgetpos does not need to flush buffers
--
Key: JRUBY-2663
URL: http://jira.codehaus.org/browse/JRUBY-2663
Project: JRuby
Issue Type: Improvement
Reporter: Wayne Meissner
On Jun 14, 2008, at 6:58 PM, Charles Oliver Nutter (JIRA) wrote:
specs hang under Apple Java 5
-
Key: JRUBY-2661
URL: http://jira.codehaus.org/browse/JRUBY-2661
Project: JRuby
Issue Type: Bug
Components:
Hirotsugu Asari wrote:
'Ant' eventually spawns 'yes', which spins CPU at near 100%. I have to
kill this 'yes' process to get the task moving forward, but must repeat
this a few times to complete the task. In the end, I have a deep (about
140 levels) stack trace, along with a reference to comm
14 matches
Mail list logo