Jruby windows 1.4RC1 users, can you test something for me? I feel like I'm going crazy

Ruby JRuby
1

Hey guys -

If you are using 1.4RC1 on windows, can you test this for me? (If it
matters
I’m using JDK 6 U 13)

just do gem install json_pure . Here is my output:

C:>jruby -S gem install json_pure
‘ure’ is not recognized as an internal or external command,
operable program or batch file.

I even tried downloading the gem and then installing it:

C:\Documents and Settings\j64lee\My Documents\Downloads>gem install
json_pure-1.
1.9.gem
‘ure-1.1.9.gem’ is not recognized as an internal or external command,
operable program or batch file.

then with the file name in double quotes:

C:\Documents and Settings\j64lee\My Documents\Downloads>gem install
“json_pure-1
.1.9.gem”
ERROR: could not find gem json|ure-1.1.9.gem locally or in a repository

I’m wondering if this is a jruby thing, or if I messed something up in
my
command prompt.

Thanks,
Jin

2

Hi Jin,

Yes, there was a regression in 1.4.0RC1, in parameter handling on
Windows (those evil BAT files).
I think I’ve already fixed that on master branch. Could you please
verify, if you can?

Thanks,
–Vladimir

On Mon, Oct 12, 2009 at 9:08 PM, Jin L. [email protected] wrote:

C:\Documents and Settings\j64lee\My Documents\Downloads>gem install

To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email
3

Yes, there was a regression in 1.4.0RC1, in parameter handling on
Windows (those evil BAT files).
I think I’ve already fixed that on master branch. Could you please
verify, if you can?

It works fine for me now [RC2].

4

Hi Roger,

On Thu, Oct 22, 2009 at 5:58 PM, Roger P. [email protected]
wrote:

Yes, there was a regression in 1.4.0RC1, in parameter handling on
Windows (those evil BAT files).
I think I’ve already fixed that on master branch. Could you please
verify, if you can?

It works fine for me now [RC2].

Thanks for verification! Yes, we fully moved away from BAT files to
the native launcher for windows, so all those weird command line
parsing errors should be all gone for good. And no more messing with
BAT files, which is a great bonus.

Not to mention that now in Task Manager you’ll see jruby.exe, not
java.exe. :slight_smile: Launching jruby.exe could be also much easier (and 3x-4x
timest faster) then jruby shell launcher on Cygwin environments.

Thanks,
–Vladimir

To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email