[geotk] code for parsing WMS Capabilities docs

[Jon Blower]

Thanks Martin.  At the moment I have a whole bunch of exclusions in my pom, as the only dependencies I need are client-wms, clients-core and xml-wms.

I am explicitly excluding the following: geotk-render, geotk-referencing, geotk-go2, geotk-coverage, geotk-utility, geotk-temporal, geotk-metadata, geotk-utility-pending, org.geotoolkit.pending, geoapi-pending and jsr-275.  Many more dependencies are explicitly excluded (if they are dependencies only of the excluded JARs).

Cheers, Jon

-----Original Message-----
From: geotoolkit-bounces at lists.osgeo.org [mailto:geotoolkit-bounces at lists.osgeo.org] On Behalf Of Martin Desruisseaux
Sent: 20 May 2010 09:06
To: geotoolkit at lists.osgeo.org
Subject: Re: [geotk] code for parsing WMS Capabilities docs

Le 19/05/10 14:46, sorel a écrit :

> That's true coverageio is not needed for the capabilities part.
> I think most dependencies are coming because of the WMSMapLayer class
> which need to know the engine, the coverage system and so on.
> If you don't intend to use it, then you can safely exclude the unwanted
> dependencies in your pom.xml.

We can also see if we can turn the dependency into an optional dependency when 
we will port this module to geotk (non-pending). Sometime it is possible to 
avoid direct dependencies with the help of META-INF/services.

	Martin
_______________________________________________
Geotoolkit mailing list
Geotoolkit at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/geotoolkit