Due to the current gap in continued funding from the U.S. National Science Foundation (NSF), the NSF Unidata Program Center has temporarily paused most operations. See NSF Unidata Pause in Most Operations for details.
Due to the current gap in continued funding from the U.S. National Science Foundation (NSF), the NSF Unidata Program Center has temporarily paused most operations. See NSF Unidata Pause in Most Operations for details.
Hello Brian Thanks for the tip! I didn't knew.The version numbers declared in the pom.xml are, to the best of my knownledge, the versions currently used by the NetCDF library. However since in this particular case an upgrate seems riskless, I took the liberty to upgrate the slf4j dependency to 1.6.1.
Martin
Le 13/12/10 19:54, Brian Schlining a écrit :
One more comment, this time about slf4j. slf4j-1.5.6 will throw an error if no binding is provided (e.g. slf4j-log4j12). So if a user forgets to add the jar containing an slf4j implementation binding to a particular logger, his/her application won't run. As of slf4j-1.6, if no binding is provided, the app will still run; the logger messages are simply discarded. 1.6.x is backwards compatible with 1.5.x ( I switched a large number of projects over with no issues at all)
netcdf-java archives: