Hello all
I'm mostly done in mavenizing the NetCDF library. The pom.xml files are at the
usual location: http://hg.geotoolkit.org/netcdf-deploy/file/tip/. Maybe it would
be useful to have them copied on the SVN?
A couple of notes:
* I used the following version numbers, please update them as needed:
- NetCDF: 4.2.5 (because I noticed that the last tag was 4.2.4)
- UnidataCommon: 4.2.5
- OpenDap: 2.2
- Grib: 8.0.27
- bufrTables: 2.0.1
- visad: 2010-08-09 (seems to be the last release date)
* I had to mavenize VisAD too. In order to build, you need to
unzip the VisAD source code in the "visad/src" directory.
* The groupID of VisAD is "edu.wisc". This is the only artifact
which is not in the "edu.ucar" group. The "edu.wisc" groupId
seems appropriate since this VisAD artifact is not modified
anymore (the "dods" package is not removed).
* If VisAD is not deployed on a Maven repository elsewhere, and
if VisAD maintainer are not willing to mavenize their project,
it may be easier to build the whole project if the VisAD source
code were copied on the NetCDF SVN repository.
* I had to track down some dependencies not listed on the
http://www.unidata.ucar.edu/software/netcdf-java/reference/JarDependencies.html
page, for example jcip-annotations, which is declared as
a Maven dependencies rather than being compiled from the
copy in the NetCDF SVN repository.
* I tested against the trunk at revision 12812. A recent change
commited on the NetCDF SVN last friday (the commit having the
"good stuff" log message) break the build, apparently because
of an API change in protobuf. I tried to upgrade the protobuf
dependencies to 2.3.0 but still get compilation failure.
In order to test the build, please see this README file:
http://hg.geotoolkit.org/netcdf-deploy/raw-file/tip/README.html
Now what is the next step? Jon, is the trunk at revision 12812 in a state stable
enough for a 4.2.5 release, or should we wait a bit? Chris, do you plan to test
and eventually deploy?
Regards,
Martin