Hey Martin,
>
> I just had a very quick look at some projects having a module with "-core" in
> their name, and it seems that "core" is used for actual Java code (i.e. those
> modules have big JAR file, and other modules are "extensions" to that core).
>
> http://repo1.maven.org/maven2/org/osgi/org.osgi.core/4.1.0/
> http://repo1.maven.org/maven2/org/apache/lucene/lucene-core/3.0.3/
> http://repo1.maven.org/maven2/org/codehaus/woodstox/woodstox-core-lgpl/4.0.9/
>
> For parent Maven module, the "<projectname>-parent" pattern seems to be used
> by
> some projects. So it could be "netcdf-parent".
Gotcha, oh OK, didn't know there was no code in there -- if there's no code and
it's just an inheritance project, I'd be +1 for netcdf-parent then. Does that
sound good everyone?
> But in my understanding the
> "unidataCommon" module has a wider scope than NetCDF. So the parent module
> could
> be "unidata-parent". Or maybe just "unidata" if all child modules are going
> to
> have a different project name anyway ("netcdf", "ncWMS", "threeds", etc.) .
Good point, but at the same time, this framework is called the "NetCDF library
for Java", even though it contains these other sub-modules which arguably
aren't necessarily only NetCDF. That said, I think it's fine to have the
project parent be called netcdf-parent, since that's the name of the library,
right?
> But actually I'm really neutral on this - this is not my project :). I will
> pickup whatever name people tell me to use.
Same here.
Cheers,
Chris
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattmann@xxxxxxxx
WWW: http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
