NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
Le 02/11/10 07:07, Mattmann, Chris A (388J) a écrit :
I think that the NetCDF community though has to decide if it wants to continue with the Ant build or to simply use Maven. I'm staying out of that holy war :) Either way we can integrate and publish to Maven Central.
I'm obviously among those we think that a Maven build would be nice, but I'm actually neutral as long as the NetCDF files make their way to a Maven repository in one way or an other.
I think there is an advantage however of having an uber jar at Central, but maybe I should name the artifact something different, like netcdf-4.2-with-dependencies.jar or something of that nature.
What about "netcdf-all" to be consistent with the naming scheme already in use on UCAR download area?
However I think that there is little advantage to put everything in the same JAR file when using Maven (quite the opposite, it can makes dependency management and convergence analysis more difficult). For Maven users, having one or many JAR files is transparent. I rather see "netcdf-all" as a pom.xml file just listing "netcdf" and all dependencies in its "<dependencies>" section. So a Maven project that depends on "netcdf-all" get everything.
If someone really wants a single JAR file with everything in it, I would assume that he is not using Maven, so maybe he would be fine to download the big JAR file from the UCAR download area?
Regards,
Martin
netcdf-java archives: