|
Sort Order:
I ran into the same problem with 1.2.4, the provided patch seems to have me going again. windows / java 1.6 / jruby rev. 4578 We need to reconcile this issue and Nick, what's the verdict on this one? I tried "JRuby Gem for GlassFish v3 10.0.0". As a result, the error occurred under the following environment. OS:Windows XP and Vista Please refer to the following blog. Kazuki: I filed your issue separately as I dont see this patch applyed neither on release 1.1.5 nor the trunk version. I'm still having issues with this, how is that this ticket got closed/fixed? It makes it frustrating for us Windows users to have to patch jruby each time we need to use it. This doesn't seem to ever have actually been resolved...so I'm reopening. After all this time, this really doesn't seem to have been resolved; so I'm assigning to 1.1.7. I also had to apply this patch to get rails 2.1 working on jruby trunk on windows vista and XP. after applying the patch rails worked fine "Me Too" With regard go having to munge this patch in to get Rails 2.2.2 apps working in weblogic on XP. Tried to run the test against jruby 1.2.0 (trunk) and everyhing looks fine: C:\jruby\bin>jruby C:\teste_bug_realpath.rb 1 tests, 1 assertions, 0 failures, 0 errors C:\jruby\bin>jruby -v I´m in a Windows Box running java 1.6 update 12 We still need confirmation of it being fixed on Windows, so leaving open for now. Thanks for the update Ruivaldo. Er, I mean weneed confirmation of rails working ok. Ahh, phooey...this one is so old that if the provided case works I'm happy marking it resolved. If it's not fixed, feel free to reopen. This still isn't fixed on trunk. If rails isn't on the current working directory, but is on the classpath root, it'll work if this patch is applied, but won't work otherwise. The attached patch fixes the issue, but isn't applied. Reopening...there's still remaining issues with this according to Ricardo, so we should actually look at the attached patch and try to apply it. For 1.2 I made a fix which corrected the test case (and I did run Rails and it worked, but that was not rails 2.3.x). [So I made a different fix than the suggested patch] The reason we have not applied this patch is it patches a library which MRI runs fine on windows. We really need test cases so we can fix it in File or some related internal utility class and not start forking standard library files (we largely just merge MRI standard libs). So any volunteers to help shake this issue out into a test case? I cannot get this to fail with Rails. Here is what I have tried [Windows XP]: 1. JRuby on C: drive, Rails app on C: drive Ricardo, I am not exactly sure I understand the scenario where Rails does not work on windows because of pathname. Can you give me some instructions? The last remaining issue has been fixed by some other fix since 1.2 (report from Ricardo – thanks for verifying this for us). Resolving. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Bug
Closed
Critical
Pathname#realpath fails for Windows drive letters
The recently launched rails 1.2.4 doesn't work with jruby. This bug seems to be the cause.