Getting a working sandbox in eclipse
Getting a working sandbox is paramount if you want to contribute to JRuby
development. This document will show you how it is done via Eclipse and
from the command-line. It will also show some of the idiosynchracies in
our project.
Part I: Eclipse
Eclipse is a popular platform for JRuby development. Most JRuby developers
use it. Because of this, we have all the eclipse settings committed in our
source tree. We can also provide assistance easier on our jruby-devel
mailing list.
Step 1: Create a new project
- Select 'File' : 'New Project...'
- Select 'CVS' : 'Checkout Projects from CVS'
- Press 'Next'
- Select 'Create a new repository location'
- Press 'Next'
- Fill out form:
- Host: cvs.sourceforge.net
- Repository Path: /cvsroot/jruby
- User: anonymous
- Password:
- Connection Type: pserver
- Use Default Port:
- Press 'Next'
- Enter 'jruby' in 'Use specified module name' field
- Press 'Finish'
At this point JRuby latest development source should be checked out into
your new project.
You will notice many errors at this point. This is because eclipse 3.1 and
earlier does not allow compiler settings to be stored in the projects local
project settings. JRuby's source uses the Java's 'assert' facility and
eclipses default settings are unhappy about this. To correct this, do the
following:
- Right click on jruby project in package explorer and select
'Properties'.
- Highlight 'Java Compiler' on left hand side of dialog.
- Select 'Enable project specific settings'.
- Set the following values on this page:
- Compiler compliance level: 1.4
- Generated .class files compatibility: 1.4
- Source compatibility: 1.4
- Select 'Ok'
- At this point a dialog should pop-up requesting a rebuild of the project
say 'Ok'
At this point you should have a clean project that builds and with any luck
has no warnings.
Part II: Command-line
TO BE WRITTEN STILL