Re: netcdf-java for maven?

Graham Leggett wrote:

On Tue, August 15, 2006 10:32 pm, John Caron wrote:

No, we looked at moving our builds to maven, and decided for now not to.
We did layout our directories in maven compatible way (I hope). Im
assuming isn not too hard, but dont have time now. Any maven gurus who'd
like to create a maven build file for us?

Hosted in a maven repository != build with maven. :)
Ahh! very good!

All that is involved, is that the published jars of the netcdf-java
project be uploaded to the right place in the website, and the dependencies for
netcdf-java are declared correctly in a descriptor file.
Is it easy to host our own jar files, or do you need to use

This allows third party projects that are dependent on netcdf-java, to
simply add notice of this dependency to their pom.xml files, after which
maven automatically downloads netcdf-java and all it's dependencies
automatically for the developer. This would be a huge potential timesaver
for users of netcdf-java who build their projects with maven.
That sounds great. One question, how does versioning work around dependencies? For example, version 2.2.17 has somewhat different dependencies than 2.2.16.

I can give it a try to get the files uploaded, I just need to know the
dependency tree of the jars published by netcdf-java - ie which jars
depend specically on which other jars, both internal to netcdf, and
external (like commons-logging, etc).

Does anyone know where I might get this information for the following files:


I assume these are the external dependencies, is this correct?

ok, heres the scoop for version 2.2.16

We create the following jar files:

 ncCore-2.2.16.jar        just the core netcdf-java classes
 netcdf-2.2.16.jar        complete netcdf-java, except for the UI and optional 
 netcdfUI-2.2.16.jar      complete netcdf-java including the UI, without 
optional libraries
 toolsUI-2.2.16.jar       complete netcdf-java including the UI and optional 
 nc2.2.jar                library that can be used in the IDV

The optional libraries:

 bufr.jar                    required to read Bufr datasets
 commons-httpclient          required to read files remotely over HTTP
 commons-logging, codec      required by commons-httpclient
 gnu-regexp                  required by dods; dods library itself is now 
directly contained in netcdf
 grib.jar                    required to read Grib-1 or Grib-2 datasets
 jdom.jar                    required to read thredds catalogs, and read NcML
 jpeg2000.jar                required to read Grib-2 JPEG2000 compressed files
 nlog4j.jar                  log4j logging. Alternately, you can use any slf4j 
 visadNoDods.jar             required to read ADDE datasets; this version has 
the dods libraries removed
 xercesImpl.jar              required to validate thredds catalogs (jdk 1.4 
 xml-apis.jar                required by xerces library

 prefsAll.jar                required for UI state persistence, related widgets
 resourcesOptional.jar       optional detailed maps and tables

The dependencies are somewhat complicated by that fast that you can leave out the optional libraries if you dont need the feature. In what follows I will assume you want all the optional features. So a dependency graph would be:


library depends on ncCore-2.2.16.jar none netcdf-2.2.16.jar bufr, commons-httpclient, gnu-regexp, grib.jar, jdom.jar, visadNoDods.jar, xercesImpl.jar (jdk1.4 only) netcdfUI-2.2.16.jar same as netcdf-2.2.16.jar, plus prefsAll.jar, resourcesOptional.jar toolsUI-2.2.16.jar none, its all in one big jar nc2.2.jar none other than whats already in the IDV

 grib.jar                  jpeg2000.jar 
 xercesImpl.jar    xml-apis.jar
 commons-httpclient        commons-logging, commons-codec


To unsubscribe netcdf-java, visit:

  • 2006 messages navigation, sorted by:
    1. Thread
    2. Subject
    3. Author
    4. Date
    5. ↑ Table Of Contents
  • Search the netcdf-java archives: