GeoTools : 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:

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 javadocs

src/

source code for project

tests/

junit tests for project

build/

target directory compile

lib/

lib populated by ant task from maven repo or ibilio

build.xml

amt build file