Re: [Geotools-devel] In anyone actually using Eclipse?

[Martin D. <mar...@no...>]

Jeff Yutzler a =E9crit :
> [...snip...].  The last is an unreachable catch block in XMLSAXHandler.

This error is caused by a slight API change in Java between J2SE 1.4 and=20
J2SE 1.5. A method (I don't remember exactly which one) was not declared=20
to throws IOException in J2SE 1.4, and the IOException declaration was=20
added in J2SE 1.5. I believe that the Geotools code expect an=20
IOException to be thrown, which means that we compile this module with=20
J2SE 1.5 (but it should run with J2SE 1.4).


> So, what is the deal with GEOAPI?  I vaguely remember this coming up=20
> months ago, but I do not remember seeing anything about it in the=20
> developer's guide.

The "geoapi-SNAPSHOT.jar" approach was causing a lot of trouble and=20
generated a fair amount of negative feedback (for good reasons) on the=20
mailing list. We changed it to dated JAR, as James said (e.g.=20
geoapi-20050403.jar for the last one). Everytime we uses an updated=20
version of GeoAPI, a copy it put there:

     http://lists.refractions.net/geotools/geoapi/jars/

Maven should pickup automatically whatever JAR version is appropriate=20
for a given SVN version. I.e. project.xml declares explicitly which=20
dated JAR is used. This means that if you go back to an older version on=20
SVN, Maven should compile against the right geoapi.jar file even if new=20
geoapi versions were published since this time.

	Martin.