It is the intention of the GRITS developers that development of the GRITS project should be IDE agnostic. However, the GRITS project began life as a project using the Eclipse IDE, and therefore instructions on getting started and set up with Elcipse are the most complete. In the future we intend to add other instructions as developers find their own favorite tools for GRITS development.
How to get started developing on the GRITS project.
CVS
You must be a SLAC GLAST developer to check out the source code from CVS. Here is an example of checking out all of grits:
$ export CVS_RSH=ssh $ cvs -d :ext:langston@centaurusa.slac.stanford.edu:/nfs/slac/g/glast/ground/cvs co grits
Directory Structure
Upon initial checkout, the GRITS project has the following directory layout. A few hidden files related to the Eclipse IDE have been omitted, as they are irrelevent to the current discussion.
build.properties build.xml resin.xml lib/ src/
The lib/ directory contains jar files needed for building and running grits. The lib/build/ directory contains all of the jar files required to compile the grits Java source code. It is this colleciton of jars you'll want to put on the CLASSPATH for whatever IDE you are using.
lib/build/*.jar lib/runtime/hibernate/*.jar lib/runtime/webwork/*.jar
The src/ directory contains all of the source code, including the Java source code, the JSP files, configuration files and deployment descriptors.
src/config/db/ src/config/middlegen/ src/java/ src/test/ src/webapp/
The Java source code lives in src/java/, while the JUnit tests for this source code lives in src/test/. The web application itseld lives in src/webapp and has the standard directory structure for a J2EE container.