Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

Nothing to see here - why? Because the work is being done on a module by module basis, and the results posted to the geotools wiki. We will post results here as they are made available.

Status

A couple of modules encountered issues early in the review process, mostly those working with propitiatory systems such as ArcSDE or Oracle where our ability to distribute jars and drivers is in question.

Provenance Review

Developers Guide

TODO:

  • Change release guide to include packaging of the user guide

Users Guide

TODO:

  • Credit each license in the user guide

Source Code

The review process has being integrated into the community development practise. A review.txt file now is provided for each module and is considered part of the source code. Initial review was completed by Jody Garnett August 7th, 2006. Adrian Custer has lead the a second review in July, 2008.

PENDING LINK TO GENERATED MAVEN SITE WITH REVIEW.TXT REPORT

Known Issues

The following issues have been identified and are recorded in our issue tracker:

com.atlassian.confluence.macro.MacroExecutionException: JIRA project does not exist or you do not have permission to view it.

Actions Taken

The following actions have been taken in response to issues raised during the iccubation process.

Turning Off Downloads

After a public email on the GeoServer list, we have chosen to turn off historical downloads of the geotools platform, and produced a new download that does not contain ArcSDE support.

We may choose to turn historical downloads on again, or issue a patch for each stable branch, depending on community needs and involvement.

Contact EPSG Providers

Frank was kind enough to contact the providers of the EPSG dataset and inform them of our difficulties in delivering the content verbatium for databases such as HSQL.

Multi License code

Some code has been donated to the the project under a range of conditions, we have chosen to include the appropriate information in a series of LICENSE.TXT files included with each binary.

We will review these files to discuss any specific needs that must be addressed in client application code, or included documentation:

  • The User Guide will credit each license
  • The User Guide will be packaged and included with each release
  • An About class will be created, and make a available a list of licenses, allowing client applications the ability to pop up a Swing Dialog as needed, or make use of their own presentation layer (say J2EE or SWT application.
  • No labels