Hi Valerio,
Regarding dependencies, it would be really useful for me if
opendap.jar (which I think is a special version for nj4?) could be
mavenized. I think (but am not sure) that this would be easy to do,
because it only depends upon commons-httpclient, unless I'm mistaken.
Regarding logging and jcl-over-slf4j, I'm not sure what's the best
decision. Dependencies on logging packages are often a problem
because this is a cross-cutting concern that might affect many parts
of the system, and classpath clashes can occur if two different
dependencies depend upon different logging systems.
> The netcdf-java pom contains the list of the dependencies needed by the
> netcdf-java library and the dependency scopes should relate to the build of
> the library itself.
I might be wrong (I'm not a maven expert) but this isn't my
understanding of how the scopes work. Sure, when you are building
netcdf-java from source using maven, you'll need a POM that includes
the compile-time dependencies correctly. But when you're *using*
netcdf-java you're not compiling it, so you need a POM that marks
run-time dependencies. The POM that you provide is for people who are
using netcdf-java, not compiling it. Please correct me if I'm wrong!
Cheers, Jon
On Fri, May 8, 2009 at 1:44 PM, Valerio Angelini <angelini@xxxxxxxxxxx> wrote:
> Hi Jon,
>
> 1) Are all the dependencies marked? For example, I was expecting to
> see a dependency on opendap.jar.
>
> Yes, not all possible dependencies are present in the POM at this time.
> Following the dependancies described in this document for the CDM Unbundled
> Library we can say that:
> - BUFR : We did not include bufr because we don't use it and it is not yet
> mavenized.
> - GRIB : this library is correctly listed in the pom and the jpeg2000 is a
> transitive dependency.
> - OPeNDAP : same as BUFR.
> - remote files over HTTP : commons-httpclient is inserted and the other
> dependencies are transitive.
> - THREDDS catalogs, NcML, BUFR, HDF-EOS, NEXRAD2, OPeNDAP : jdom is present.
> - McIDAS AREA : same as BUFR.
> If someone needs the libraries we don't directly include, we could give a
> write-enabled account of our repository to a developer that mavenizes the
> other libraries and consequently we will include them as well.
> NOTE:
> For a consisten usage of slf4j we are thinking of exclude the
> commons-logging from the commons-httpclient dependency and introduce
> the jcl-over-slf4j.
> What do you think about it?
>
> 2) Could some of the dependencies be marked with a runtime scope?
> From previous emails in this thread it seems that jdom is the only
> dependency that's needed at compile time.
>
> The netcdf-java pom contains the list of the dependencies needed by the
> netcdf-java library and the dependency scopes should relate to the build of
> the library itself.
> Following this principle we think that the libraries currently present in
> the POM are correctly scoped, because they are directly referenced in the
> netcdf-java sources.
> Regards
> Valerio
>
>
> --
> Valerio Angelini
> Institute of Methodologies for Environmental Analysis
> Italian National Research Council
> phone: +39 0574 602535
> e-mail: angelini@xxxxxxxxxxx
>
>
>
--
Dr Jon Blower
Technical Director, Reading e-Science Centre
Environmental Systems Science Centre
University of Reading
Harry Pitt Building, 3 Earley Gate
Reading RG6 6AL. UK
Tel: +44 (0)118 378 5213
Fax: +44 (0)118 378 6413
j.d.blower@xxxxxxxxxxxxx
http://www.nerc-essc.ac.uk/People/Staff/Blower_J.htm
