Added by jgarnett, last edited by jgarnett on Aug 20, 2007  (view change)

Labels

 
(None)

There are two methods of aquiring the GeoAPI source code:

Download sources and binary

Stables releases can be downloaded from SourceForge FTP servers.
Milestones can be downloaded from the GeoAPI main page.

The download is a ZIP file containing:

  • The Java source code (see the Compile page).
  • The javadoc as a set of HTML pages.
  • The binaries (compiled class files) as two JAR files:
    • geoapi.jar: the standard JAR targeting the Java standard environment version 1.4 or later.
    • geoapi-tiger.jar: a JAR targeting the Java environment version 1.5 or later.
      This JAR is identical to geoapi.jar except that it includes generic type information and annotations, and also uses covariant return types.

Developers who don't need the "bleeding edge" GeoAPI's features are encouraged to link against one of those two JAR files, instead of working from the SVN. The javadoc can be browsed online before downloading. The build date in the upper right corner provides a way to check if a newer version is available for download.

From Source Forge SVN

SVN (SubVersion) stores the source code in a centralized location. SVN is designed as a tool for developers; the source code stored in SVN should be thought of as "bleeding edge". If you are simply looking for the latest version of GeoAPI, you should check the project's download page before retrieving data from SVN.

If you just have an interest in contributing, then the latest SVN version is often ideal, since it should include any fixes made since the most recent stable release.

Anonymous SVN access (Read Only)

The project's SourceForge.net SVN repository can be checked out through anonymous SVN with the following instruction set.

svn checkout https://geoapi.svn.sourceforge.net/svnroot/geoapi/trunk geoapi

NOTE: UNIX file and directory names are case sensitive. The path to the project SVNROOT must be specified using lowercase characters (i.e. /svnroot/geoapi). Information about accessing this SVN repository may be found in the document titled, Subversion (Version Control for Source Code).

Outdated instructions

Instructions below this point are outdated, since they relate to the old CVS system.

Developers CVS (Read Write)

This time we will connect to:

cvs.sf.net:/cvsroot/geoapi

But there is a trick - you will need to use ssh to pull it off.

This time we will use Eclipse to illustrate connection:

You can use the above settings in your application of choice. If you are using command line ssh rsh tunneling please refer to the source forge docs to set this up.

Checking out GeoAPI for Eclipse Development

Eclipse is not going to play nice when it comes to checking out GeoAPI, it only check's out project folders (and as you can see above the top level folder is not going to work).

GeoAPI
  1. Create a new Java Project called GeoAPI
    • JDK Complience: 5.0
    • Project layout: Create separate source and output folders
    • Press Finish (we will come back to this)
  2. Check out the src directory into your GeoAPI project
    1. Open up CVS Perspective and right click on the HEAD > src
    2. Select Checkout As...
    3. Check Check out into an existing project and press Next
    4. Target folder name: src, select GeoAPI as the parent, and press Next
    5. Select a tag: HEAD and press Finish
      • A dialog will prompt you that the existing src folder will be deleted, this is what we want.
GeoAPI Pending
  1. Create a new Java Project called GeoAPI Pending
    • JDK Complience: 5.0
    • Project layout: Create separate source and output folders
    • Press Finish (we will come back to this)
  2. Check out the src directory into your GeoAPI project
    1. Open up CVS Perspective and right click on the HEAD > src
    2. Select Checkout As...
    3. Check Check out into an existing project and press Next
    4. Target folder name: src, select GeoAPI Pending as the parent, and press Next
    5. Select a tag: HEAD and press Finish
      • A dialog will prompt you that the existing src folder will be deleted, this is what we want.
  3. Check out the examples directory into your GeoAPI Pending project
    1. Open up CVS Perspective and right click on the HEAD > examples
    2. Select Checkout As...
    3. Check Check out into an existing project and press Next
    4. Target folder name: examples, select GeoAPI Pending as the parent, and press Next
    5. Select a tag: HEAD and press Finish

It is hoped that when we move to subversion the geoapi repository can be set up based on Maven which contains a eclipse target.