JRuby 1.6.5 and Cucumber incompatible on Windows 7(x64): load error: 
gherkin/i18n -- org.yaml.snakeyaml.reader.ReaderException
------------------------------------------------------------------------------------------------------------------------------

                 Key: JRUBY-6223
                 URL: https://jira.codehaus.org/browse/JRUBY-6223
             Project: JRuby
          Issue Type: Bug
          Components: Ruby 1.9.2, Windows
    Affects Versions: JRuby 1.6.5
         Environment: Windows 7 Professional; 64-bit OS, 8GB RAM, 2 Quad CPU
Java:  version "1.6.0_20"
         Java(TM) SE Runtime Environment (build 1.6.0_20-b02)
         Java HotSpot(TM) Client VM (build 16.3-b01, mixed mode, sharing)
JRuby 1.9 compatibility mode
            Reporter: Ralph Bohnet
            Assignee: Thomas E Enebo
            Priority: Blocker
         Attachments: jruby-bug.zip

Similar to JRUBY-6200, only this has no dependency on rails.  Attached a simple 
cucumber files that reproduce this behavior.

Installed JRuby (windows executable(x64) or jruby-bin-1.6.6.zip) and then 
installed / updated rubygems, bundler, and cucumber.
When we turn on 1.9 compatibility mode and attempt to run cucumber via bundler, 
it complains that it cannot find the cucumber script.  If the cucumber script 
is passed directly to jruby instead of via bundler, then the following error 
appears:
  load error: gherkin/i18n -- org.yaml.snakeyaml.reader.ReaderException: 
special characters are not allowed
   (full stack trace below)

Steps to reproduce this issue:

1. Install JRuby 1.6.5 on windows 7 (set JRUBY_HOME=[install dir])

2. Open command window and run:

    jruby --1.9 -S gem install rubygems-update
    jruby --1.9 -S gem update --system
Error opening script file: C:/temp/jruby-bug/setup.rb (The system cannot find 
the file specified)

    cd  %JRUBY_HOME%\lib\ruby\gems\1.8\gems\rubygems-update-1.8.11
    jruby --1.9 -S setup.rb
       (updated RubyGems to 1.8.11)
   
   cd [location of attached sample] 
    jruby --1.9 -S gem install bundler --no-rdoc --no-ri

     jruby --1.9 -S bundle install
       (all gems installed successfully)

     jruby --1.9 -S bundle show cucumber
         (displays %JRUBY_HOME%/lib/ruby/gems/1.9/gems/cucumber-1.1.2)

     jruby --1.9 -S bundle exec cucumber
           error generated:
           bundler: command not found: cucumber
           Install missing gem executables with `bundle install`

  Try using the cucumber command directly:
     jruby --1.9 -S %JRUBY_HOME%/lib/ruby/gems/1.9/bin/cucumber 

also get the same error (below) if I just run:
     jruby --1.9 -S bundle console

Output:
C:/jruby-1.6.5/lib/ruby/gems/1.8/gems/gherkin-2.6.5-java/lib/gherkin/i18n.rb:9 
warning: already initialized constant FEATURE_ELEMENT_KEYS
C:/jruby-1.6.5/lib/ruby/gems/1.8/gems/gherkin-2.6.5-java/lib/gherkin/i18n.rb:10 
warning: already initialized constant STEP_KEYWORD_KEYS
C:/jruby-1.6.5/lib/ruby/gems/1.8/gems/gherkin-2.6.5-java/lib/gherkin/i18n.rb:11 
warning: already initialized constant KEYWORD_KEYS
LoadError: load error: gherkin/i18n -- 
org.yaml.snakeyaml.reader.ReaderException: special characters are not allowed
  require at org/jruby/RubyKernel.java:1047
   (root) at 
C:/jruby-1.6.5/lib/ruby/gems/1.8/gems/gherkin-2.6.5-java/lib/gherkin/lexer/i18n_lexer.rb:1
  require at org/jruby/RubyKernel.java:1047
   (root) at 
C:/jruby-1.6.5/lib/ruby/gems/1.8/gems/gherkin-2.6.5-java/lib/gherkin/lexer/i18n_lexer.rb:1
  require at org/jruby/RubyKernel.java:1047
   (root) at 
C:/jruby-1.6.5/lib/ruby/gems/1.8/gems/gherkin-2.6.5-java/lib/gherkin.rb:5
  require at org/jruby/RubyKernel.java:1047
   (root) at 
C:/jruby-1.6.5/lib/ruby/gems/1.8/gems/cucumber-1.1.2/bin/../lib/cucumber/cli/main.rb:11
     load at org/jruby/RubyKernel.java:1073
   (root) at C:\jruby-1.6.5\lib\ruby\gems\1.8\bin\cucumber


--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply via email to