Hi John,
Perhaps it is a good idea to add dependant packages to the netcdf jar file?
Or perhaps logging the core packages could use just the default jdk logging?
Just a thought...
-C
__________________________________________________________________
Christopher W. Moore email: Christopher.Moore@xxxxxxxx
Research Scientist, Oceanography tel: 206.526.6779
University of Washington/JISAO/NOAA-PMEL fax: 206.526.6744
NOAA Center for Tsunami Research Seattle, WA
------------------------------------------------------------------
On Wed, 3 Jan 2007, John Caron wrote:
oops, sorry:
We have pushed logging facilities down into even the core packages. This
means that you need to add an SLF4J logging implementation to your classpath.
The simplest/smallest is
ftp://ftp.unidata.ucar.edu/pub/netcdf-java/slf4j-jdk14.jar
which uses the default jdk1.4 logging. The other likely choice is one using
Log4J:
ftp://ftp.unidata.ucar.edu/pub/netcdf-java/nlog4j-1.2.21.jar
which is widely used, especially at the enterprise level.
I apologize for not making this new dependency clear; it is now documented on
the netcdf-java home page.
John
Jochen Deyke wrote:
John Caron wrote:
Hi Jochen :
Thanks for pointing out, it should be fixed now.
I now get this instead:
java.lang.NoClassDefFoundError: org/slf4j/LoggerFactory
2.2.16 used to complain of missing libraries as well, but just worked
anyways. Now, the error is all I get.
==============================================================================
To unsubscribe netcdf-java, visit:
http://www.unidata.ucar.edu/mailing-list-delete-form.html
==============================================================================
==============================================================================
To unsubscribe netcdf-java, visit:
http://www.unidata.ucar.edu/mailing-list-delete-form.html
==============================================================================
