Hi folks,
I've refactored our jruby.1.8.mspec and jruby.1.9.mspec config files
so that it would be easier to reuse them when executing the mspec CI
runs from outside of JRuby repo. The goal was to minimize additional
configuration needed to execute rubyspecs from external, standalone
repository. Working with standalone rubyspecs is usually better, more
convenient than working with JRuby's version (there is no fear of
accidental deletion of changes, etc).
So, with ce2e7ce019fd9 commit, it gets trivial to execute mspec ci
runs from standalone repository:
Create jruby.1.8.mspec or jruby.1.9.mspec files in that standalone 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.
Running in 1.9 mode is also simple:
jruby --1.9 -S mspec ci
Thanks,
--Vladimir
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
