going forward

We made some recomendations for long term handling of plug-ins and extensions.

Here is what that looks like under the cold hard truth of a repository structure.

Repository:

gt/
arcsde/
geomediaimplemenation/   what is geomedia?
gtopo30/
mysql/
oracle/
postgis/
shapefile/
tiger/
graph/
validation/
demos/

The structure of the gt project:

design/                  Replace with wiki and recent aaime uml diagrams?
doc/                     Is this the website generation?
module/main**            Merged modules from the required list
module/mapinfo/          Orphan
module/resources/        Orphan
module/svgsupport/       Orphan
module/imagedatasource/  Orphan
module/vpf/              Orphan
module/utils/            Orphan
module/sample-data/      Orphan
module/legend/           Orphan
buildlist.txt
geotools_checks.xml
build.properties
GT2Eclipse.java
maven.xml
navigation.vm
project.xml              root maven project file
README.txt
requiredList.txt
run-maven.xml

The structure of the other projects can be as the see fit:

• ant based?
• can we make an ant task for downloading gt jars from from Maven or Ibilio?

doc/                      documentation for project
doc/api                   (generated) generated javadocs
src/                      source code for project
tests/                    junit tests for project
build/                    (generated) target directory compile
lib/                      lib populated by ant task from maven repo or ibilio
build.xml                 ant build file