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.
Hello Chris Le 08/12/10 08:07, Mattmann, Chris A (388J) a écrit :
Can we get my build patch committed to integrate the mvn dist/deploy target as part of this release?
Sure, can you remind me what the patch was please?
I will try to test today on my local machine that NetCDF work with the minimal dependencies listed in my previous email. Then I will let you know.I'd be happy to RM the release and coordinate the release of the artifacts to Central with you. Just let me know.
For OpenDap, maybe we can do a separated deployment (after NetCDF) anyway? If we agree that the "netcdf" artifact shall contains the minimal core with all optional dependencies omitted, then OpenDap would be a separated artifact that developer needs to declare explicitly in their pom.xml file if they wish to use OpenDap with NetCDF?
The rational is that (in my understanding) OpenDap is optional, and it is easier for a developer to add dependencies than to remove them.
Martin
netcdf-java archives: