Sure, +1, go for it Martin. I tried making the RC but stalled on some weirdness in the mvn:release plugin. So go for it.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: [email protected] WWW: http://sunset.usc.edu/~mattmann/ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -----Original Message----- From: Martin Desruisseaux <[email protected]> Organization: Geomatys Reply-To: "[email protected]" <[email protected]> Date: Monday, July 8, 2013 8:53 AM To: Apache SIS <[email protected]> Subject: <groupId> to reflect the directory structure? >Hello all > >I tried today a mini-deployment on an experimental repository. I noticed >a minor discrepancy between the <groupId> of "core", "storage" and >"application" directories: > >* All modules in "storage" have the "org.apache.sis.storage" groupId. >* All other modules have the "org.apache.sis" groupId, regardless of >their parent module and directory. > >Should we change the <groupId> of "core" modules from "org.apache.sis" >to "org.apache.sis.core", and likewise for "application" modules? This >change would take just 10 minutes to apply, but if we do it, it would be >cleaner to do it before the release. > >Note: Maven seems to do something similar for plugins (i.e. all Maven >plugins have the "org.apache.maven.plugins" groupId), except that they >have no "core" directory - core modules are in the parent (project root) >directory instead. > > Martin >
