Le 05/05/13 23:31, Mattmann, Chris A (398J) a écrit :
Let's have:
sis-storage
sis-kml
sis-netcdf
sis-shapefile
What about the following?
storage (without "sis-" prefix)
sis-kml
sis-netcdf
sis-shapefile
The reason is that "storage" is not a JAR module, but only a POM
referencing sub-modules. If we keep the convention that only "real" JAR
modules have the "sis-" prefix, then it makes clear which directories
are JAR modules and which directories are groups for JAR sub-modules.
Furthermore it would keep the "sis-storage" name available for a real
JAR module if we want to put "storage core" code in it.
In addition, "storage" sub-modules could also have the
"org.apache.sis.storage" groupId instead of only "org.apache.sis". If we
do that way, the Maven repository would contains a sub-directory named
"storage" with both the pom.xml definitions, and the sub-modules as
"sis-kml", "sis-netcdf", etc. sub-directories. So the groupId, the
package name, the directory tree in source code and the directory tree
on the Maven repository after deployment would all be consistent.
Martin
