Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: JRuby 1.0.0RC3
-
Component/s: None
-
Labels:None
-
Number of attachments :
Description
Rake is an absolute standard for almost all Ruby development. RSpec is fast becoming the standard way to specify and test applications. We believe both should be included in the base install of JRuby, and so we should add them into our repository.
Rake is at version 0.7.3 and RSpec is at version 1.0.0. RSpec passes all its specs now. It would be good to make an effort to get Rake's tests closer to 100% as well.
I'm on the fence as to whether we should commit RSpec and Rake in SVN, or just have them install as part of "dist" and "test" targets. I don't feel right about committing packages in the local repo to SVN.
Activity
I've seen that quite a few of the Jakarta projects have their Ant builds set up to download dependent JARs from somewhere (usually a Maven repo). How about a little Ant task that calls JRuby to call something in the rubygems module to fetch the Rake and RSpec gems as part of the build? Probably overkill. 
First: Thanks a ton for deciding to include RSpec in JRuby. It's going to be interesting to see how people will use RSpec with Java objects.
Ola showed me some minor quirks in RSpec's own specs that were a hindrance for 100% green on JRuby. I've just committed fixes for all of these, so hopefully everything is ok now. Those fixes will be in 1.0.1. Give us a heads up and we can release it before you push out 1.0.0.
I agree that it's a little dirty to check in copies of Rake/RSpec source into your svn. Perhaps a pragmatic middle ground is to just check in the gem files? Or was that what you meant?