Hello all
I have re-organized the SIS modules in "core", "storage" and
"application" groups as suggested by emails. I would recommend anyone
having a svn checkout to perform "mvn clean" *before* "svn update", in
order to avoid orphan "target" directories in the workspace.
I also took the initiative to rename "sis-parent" as "parent" for
consistency with all other groups, which have no "sis-" prefix. This
change should be invisible to users since I don't think there is any
reason why a user would reference this pom directly. However I can
revert if peoples think we should.
I did not changed the "groupId" of modules. Consequently the
<dependency> declaration in Maven projects using SIS is unchanged. We
currently have:
* org.apache.sis.storage groupId for sis-netcdf
* org.apache.sis for all other modules.
Whether the groupId should reflect the directory structure for all
modules is an open question. I'm neutral on that. I'm not sure it is
worth for "core" module. It may be considered for "application" modules,
but their names ("sis-app" or "sis-webapp") is already explicit...
Martin
Le 07/05/13 15:28, Mattmann, Chris A (398J) a écrit :
+1 makes sense to me. We've got time so lets update for 0.3...
On May 7, 2013, at 1:46 AM, "Martin Desruisseaux"
<[email protected]> wrote:
(...snip...)
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
- ...
