Hello Everyone, The structure of the project in terms of submodules is overly complex and some names are confusing (e.g. baremaps-database, baremaps-postgres). Also, as we start doing releases, having a lot of submodules published on the maven repository may complicate things when searching for artifacts. I guess the structure of the project is one of the pains encountered by new comers and simplifying it may help. Here is a proposal for a revised structure and I would love to discuss it: - baremaps-benchmarks - baremaps-cli - baremaps-engine (single module with subpackages?) - org.apache.baremaps.collection - org.apache.baremaps.geocoder - org.apache.baremaps.iploc - org.apache.baremaps.osm - org.apache.baremaps.postgres (to be merged with org.apache.baremaps.database?) - org.apache.baremaps.storage (to be renamed formats or codec?) - org.apache.baremaps.stream (utilities to deal with large streams) - org.apache.baremaps.workflow - baremaps-http (to be renamed server?) - baremaps-testing
Should we take care of this before the first release? Best, Bertil --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@baremaps.apache.org For additional commands, e-mail: dev-h...@baremaps.apache.org
