...
The third part would continue as the gt-app-schema module. The first part will be moved to gt-main. More specifically, the following classes will be moved:
- org.geotools.feature.AttributeBuilder (PARTLY)org.geotools.feature.TypeBuilder
- org.geotools.util.ComplexAttributeConverterFactory
- org.geotools.feature.Types (PARTLY)
The second would split off and become a new module 'gt-complex'. More specifically, this 'gt-complex' module will consist of the following classes that are now in the gt-app-schema module.
- org.geotools.feature.AttributeBuilder (PARTLY)
- org.geotools.filter.expression.FeatureProperty + complete org.geotools.feature.xpath package
- complete org.geotools.feature.type package
- org.geotools.feature.Types
- org.geotools.data.complex.filter.XPath (PARTLY)
- org.geotools.data.complex.FeatureTypeRegistry (PARTLY) + depending classes (for building types from xsd)
...
- AttributeBuilder - will still need an extended version in app-schema to support the NonFeatureTypeProxy which uses mappings
- XPath , Types - is are just a class classes of different static methods that need to be split in two
- FeatureTypeRegistry will be made more generic using a helper interface 'FeatureTypeRegistryHelper, app-schema can have its specific implementation
...