Justin Deoliveira a écrit :
> However, after looking into how other projects with many modules like
> geotools they all use a prefix such as we are doing now. See commons,
> hibernate, spring.
I had a little bit of hesitation too. However removing the prefix from module
name (and configure Maven's <finalName> instead) brings an interresting feature:
Jody suggested to take the opportunity for using a prefix that distinguish
between supported and unsupported JARs. It sound like a great idea to me. If we
do so, removing the prefix and using <finalName> instead allows us to change a
module category (e.g. from "unsupported" to "plugin") and change the JAR prefix
without changing the module name (so Maven dependencies are not broken).
If we go ahead with Jody's idea, we need to agree about prefix. What about the
following ones?
modules/library: gt-lib-
modules/plugin: gt-plg-
modules/extension: gt-ext-
modules/unsupported: gt-uns-
build/maven gt-mvn-
build/(other) gt-build-
demo/* gt-demo-
Martin
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
