It seems this is actually related to the java package name containing
'context'. I've posted a rspec bug for this along with a simple case
to demonstrate. I realize this may wind up kicked over to the JRuby
people...
http://rspec.lighthouseapp.com/projects/5645-rspec/tickets/728-rspecjruby-
We've seen this behavior again, this time with rspec-1.1.12 and jruby
1.2.0RC1; the common factors seem to be:
(1) jruby
(2) rspec 1.1.11 or 1.1.12
(3) naming a java class with the string 'context' or 'Context' in its name.
In this case the bit of ruby causing trouble was:
SecurityContex
I just got bitten by a strange issue with rspec-1.1.11 and jruby
1.1.3-1.1.6RC1. I'd love to know what the problem was if anyone has
any ideas. It's almost as if, rspec didn't like something about this
particular class since substituting others worked fine. It does work
with Rspec edge so I
