Re: [Geotools-devel] Splitting main

[Jody G. <jga...@re...>]

Martin Desruisseaux wrote:
> I'm considering splitting module/main in three parts:
> 
> 
>  * module/referencing  would contains:
>    - org.geotools.referencing
>    - org.geotools.metadata  (because metadata and ref. need each other)
>    - org.geotools.parameter
>    - org.geotools.factory   (support classes)
>    - org.geotools.resources (support classes)
>    - org.geotools.util      (support classes)
>    - org.geotools.io        (support classes)
> 
> 
>  * module/coverage     would contains:
>    - org.geotools.coverage
>    - org.geotools.image
> 
> 
>  * module/main         would contains:
>    - everything else for now
> 
> 
> The hope is to avoid a 3 Mb download for projects using only the 
> referencing part, or to make a smaller download for projects that 
> doesn't use the coverage part (and maybe isolate the JAI dependency in 
> module/coverage only if we can).
> 
> The change would be applied on trunk only.

Can you publish a milestone release when you merge this change into 
trunk? (I suspect you would do this on a branch first?) I would like to 
start chris holmes of idea of a change equals a release (bug fixes need 
not apply).

> Does it make sense? Any agreement/disagreement?

It makes sense, I have my own ideas to split main:
- interfaces into a separate project (geoapi where possible, gtapi for 
transition)
- implementation in geotools like normal

Looking at your "split" above module/referencing and module/coverage are 
the ones that have most of their interfaces moved to geoapi already?

So Martin until the PMC (you and me included) decide an actual plan I 
have to vote -1 one this.  Can we swap email for a bit and do something 
that will make sense in the long term...

At the very least I would like to see the breakdown in GeoTools broken 
down by layers (which you have started to do), I just need it to make 
sense for people learning.

As an example you cannot break out module/coverage in that manner - 
coverage *needs* to extend Feature (actually BoundedFeature). The fact 
that we hide that association with the same code snippit in J2D and 
LiteRenderer is not very respectful of the data model.

Jody