sure, thanks. Gabriel Gabriel Roldan wrote: > mvn dependency:tree gave me the answer: > [INFO] | \- org.geotools:gt-metadata:jar:2.6-SNAPSHOT:compile > [INFO] | +- java3d:vecmath:jar:1.3.1:compile > [INFO] | +- org.opengis:geoapi:jar:2.3-SNAPSHOT:compile (version > managed from 2.3-M1) > [INFO] | | \- net.java.dev.jsr-275:jsr-275:jar:1.0-beta-2:compile > [INFO] | +- org.opengis:geoapi-pending:jar:2.3-SNAPSHOT:compile > (version managed from 2.3-M1) > [INFO] | \- javax.measure:jsr-275:jar:0.9.1:compile > > Shall I update gt-metadata to the same version geoapi requires and > commit? (commenting out the dependency on gt-metadata and relying on the > transitive one from geoapi seems to work) > > Gabriel > Gabriel Roldan wrote: >> I found GeoServer trunk does not work on Tomcat but does on Jetty. >> Reason being there are two jsr-275 jars on geoserver/WEB-INF/lib: >> jsr-275-0.9.1.jar and jsr-275-1.0-beta-2.jar. >> >> So it will work or not depending on which one is first picked up by the >> classloader. >> >> Any clue on how to solve it? >> >> Cheers, >> Gabriel >> >> Ben Caradoc-Davies wrote: >>> Simone Giannecchini wrote: >>>> Please, reopne the ticket, I will see what I can do to make use of one >>>> of the standard jars on the jsr-275 website. >>> I have reopened it. >>> >>> We should be able to set the new artifact version in dependency >>> management. The problem is that 1.0.0 pom appears to redirect to 0.9.1, >>> which contains less than 1.0-beta-2. If you can get a single jar used >>> across GeoTools, and a maven build passes, eclipse will most likely be >>> happy. >>> >>> Kind regards, >>> >> > >
-- Gabriel Roldan OpenGeo - http://opengeo.org Expert service straight from the developers. ------------------------------------------------------------------------------ _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
