Bugs item #17837, was opened at 2008-02-06 21:46 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=7857&aid=17837&group_id=2014
Category: None Group: None >Status: Closed Resolution: None Priority: 3 Submitted By: GlassFish JRuby (glassfishgem) Assigned to: Nobody (None) Summary: Yaml parsing error with application in JRuby (war format of application) Initial Comment: This is the error that a partner is seeing when they try to port their application to a JRuby + GlassFish V2 (using Goldspike) environment. The jruby version that they are using is : ruby 1.8.6 (2008-02-03 rev 5512) [i386-jruby1.1RC1] >> >> We get this error. It is from GemInstaller (which I wrote). It seems >> to have problem parsing the yaml file under jruby, but this problem >> never exists under standard ruby. Seems like a problem with the YAML >> parsing in jruby? >> >> 008-02-05 18:08:41.653:/pivots-jruby-spike:INFO: Failed to load >> Rails: Error: Received error while attempting to parse YAML from yaml >> text: >> ScannerException while scanning a block scalar we had this expected >> chomping or indentation indicators, but found =(61) >> Please ensure this is valid YAML: >> >> --- >> defaults: >> install_options: -y >> gems: >> - name: ActiveRecord-JDBC >> version: 0.5 >> - name: activerecord-jdbcmysql-adapter >> version: 0.7 >> - name: aws-s3 >> version: 0.3.0 >> - name: capistrano-ext >> version: 1.2 >> - name: capistrano >> version: 2.0 >> - name: flexmock >> version: 0.6.0 >> - name: rails >> version: 2.0.2 >> - name: mime-types >> version: 1.15 >> - name: hpricot >> version: 0.5 >> - name: geminstaller >> version: >= 0.3.0 >> - name: gmailer >> version: 0.1.6 >> - name: mechanize >> version: 0.6.8 >> - name: rmagick >> version: 1.15.10 >> - name: ruby-debug >> version: >= 0.9.3 >> - name: has_finder >> version: 0.1.5 >> - name: json >> version: 1.1.0 >> - name: jruby-openssl >> version: 0.1.1 >> - name: markaby >> version: 0.5 >> >> >> " >> >> >> /home/pivotal/workspace/pivots-jruby-spike/WEB-INF/gems/gems/geminstaller-0.3.0/lib/geminstaller/yaml_loader.rb:17:in >> `load' >> >> /home/pivotal/workspace/pivots-jruby-spike/WEB-INF/gems/gems/geminstaller-0.3.0/lib/geminstaller/config_builder.rb:34:in >> `build_config' >> >> /home/pivotal/workspace/pivots-jruby-spike/WEB-INF/gems/gems/geminstaller-0.3.0/lib/geminstaller/config_builder.rb:31:in >> `each' >> >> /home/pivotal/workspace/pivots-jruby-spike/WEB-INF/gems/gems/geminstaller-0.3.0/lib/geminstaller/config_builder.rb:18:in >> `build_config' >> >> /home/pivotal/workspace/pivots-jruby-spike/WEB-INF/gems/gems/geminstaller-0.3.0/lib/geminstaller/config_builder.rb:31:in >> `create_gems_from_config' >> >> /home/pivotal/workspace/pivots-jruby-spike/WEB-INF/gems/gems/geminstaller-0.3.0/lib/geminstaller/application.rb:42:in >> `autogem' >> >> /home/pivotal/workspace/pivots-jruby-spike/WEB-INF/gems/gems/geminstaller-0.3.0/lib/geminstaller.rb:28:in >> `autogem' >> >> /home/pivotal/workspace/pivots-jruby-spike/config/../vendor/plugins/pivotal_core_bundle/lib/geminstaller/geminstaller_boot.rb:37 >> /home/pivotal/workspace/pivots-jruby-spike/config/boot.rb:18:in >> `require' >> /home/pivotal/workspace/pivots-jruby-spike/config/boot.rb:18 >> /home/pivotal/workspace/pivots-jruby-spike/config/environment.rb:2:in >> `require' >> /home/pivotal/workspace/pivots-jruby-spike/config/environment.rb:2 >> :1 >> >> javax.servlet.ServletException: Could not load Rails. See the logs for >> more details. >> at org.jruby.webapp.RailsFactory.makeObject(RailsFactory.java:139) >> at >> org.jruby.webapp.util.CustomObjectPool.addObjectInternal(CustomObjectPool.java:111) >> at >> org.jruby.webapp.util.CustomObjectPool.access$200(CustomObjectPool.java:15) >> at >> org.jruby.webapp.util.CustomObjectPool$PoolSizeManager.run(CustomObjectPool.java:193) >> 2008-02-05 18:08:41.925::INFO: Shutdown hook executing >> 2008-02-05 18:08:42.041::INFO: Shutdown hook complete >> > ---------------------------------------------------------------------- >Comment By: Ola Bini (olabini) Date: 2008-02-12 13:08 Message: This has been fixed on JRuby trunk. ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=7857&aid=17837&group_id=2014 _______________________________________________ Jruby-extras-devel mailing list [email protected] http://rubyforge.org/mailman/listinfo/jruby-extras-devel
