* Add autoloaded warning for "Config" constant * Clean up references to "Config" in files potentially touched in 1.9 mode * Update missing/divergent stdlib files * Remove all 'syck' code from 1.9 stdlib * Add warning to 'ripper' lib * Copy over missing matrix/ files
Update to latest RubySpec, update tags for 1.9.
Removed excluldes of non-existing libraries, reorganized the mspec config files (explicit excludes now instead of explicit includes before). All excluded libraris with unknown reasons for the exclusions are organized together in a single block, to remove it later on.
Now, it is much easier to run 'mspec ci' from a standalone rubyspec repo: Create jruby.1.8.mspec or jruby.1.9.mspec files in that rubyspec repository, define SPEC_DIR and/or TAGS_DIR and load the main mspec file from the JRuby repo. Like this: ======== jruby.1.8.mspec in standalone repo =========== SPEC_DIR = File.dirname(__FILE__) load '/opt/work/jruby.git/spec/jruby.1.8.mspec' ======== end of file ================================= Now, doing 'jruby -S mspec ci' from that standalone rubyspec repo will just work as expected, executing the specs from that repo, but with the exclusions from the main JRuby repo.
…'s mspec config
…les for 1.8 and 1.9 tags dirs.