Excellent! These items should probably be migrated to the wiki too once they are implemented. Also, I just noticed that our Jira page is still referencing the URL for the incubator site[1]. I don't have the permissions to fix it...Logged a Jira issue here[2].
Adam [1] https://issues.apache.org/jira/browse/SIS [2] https://issues.apache.org/jira/browse/SIS-99 On May 7, 2013, at 4:45 AM, Martin Desruisseaux wrote: > Hello Chris > > Le 07/05/13 01:20, Mattmann, Chris A (398J) a écrit : >> +1, but we should probably make all top level dirs consistent like this >> then too, right? > > In this proposal, the presence or absence of "sis-" prefix in directory name > would not be determined by whether the directory is top-level or not, but > rather by whether the directory is for a module producing a JAR file or is > just a container for such sub-modules. Or in other words, it would be > determined by whether the directory is a leaf in the modules tree or not. > Only leaves would have "sis-" prefix. > > In terms of Maven pom.xml, this would be determined by the <packaging> > element. "pom" packaging would have no "sis-" prefix, because they produce > nothing by themselves. "jar", "bundle" and "maven-plugin" packaging would > have the "sis-" prefix. > > If nevertheless we want to have top-level directories that looks like > consistent, one possible approach could be to group the current top-level > modules (except the "app" ones) in a "core" group. So the hierarchy could be > like below: > > core > - sis-utility > - sis-metadata > - sis-referencing > - sis-coverage > - ... > storage > - sis-shapefile > - sis-geotiff > - sis-postgis > - sis-netcdf > - ... > client > - sis-wms > - sis-wfs > - sis-csw > - ... > application > - sis-app > - sis-webapp > - ... > > > So the "core" which existed in SIS 0.2 would be back, but as a group of > modules rather than a single one. > > What do you think? > > Martin >
