| Re: [udig-dev] testing of 2.0 SNAPSHOT |
Right, great research we can work with! As a short answer from vacation I would suggest to create an issue for it de can split Ingo subtask. This would help us later to explain THW why's and how we solved these
I'll be back next week
- Frank
Excellent comparison testing ...I am not totally sure on the differences between jars as we have not been tracking geotools and geoscript development that closely. It is also likely that I missed including (or excluding) things such as scala.My goal was to test the wfs work Niels was doing as soon as possible - it has been so long since anyone worked on WFS client, let alone write a complete replacement!A few other comments inline...antlr-2.7.7.jar antlr-2.7.7.jarantlr-3.3.jar antlr-runtime-3.3.jarantlr-runtime-3.3.jarAntlr is confusing, and likely to remain so for a bit. If possible I would prefer to use the antlr-runtime which requires additional jars (rather than antlr which includes several jars).asm-3.2.jarasm-analysis-3.2.jarasm-commons-3.2.jarasm-tree-3.2.jarasm-util-3.2.jarNot sure what this one is ...commons-dbcp-1.3.jar commons-dbcp-1.4.jarThis is likely to get upgrade shortly as GeoTools has reached the limit of the current connection pool implementation.geocss_2.10-0.8.3.jarNot sure what this one is.google-collections-0.8.jarThis has been replaced with guava near as I understand it.groovy-1.8.8.jar groovy-all-2.2.2.jarWe should be using groovy (and figuring out what jars it needs, rather than groovy-all which includes a copy of antlr.gt-geopkg-12-SNAPSHOT.jarHow did he sneak in? Probably a geoscript dependency.gt-shapefile-9.0-M0.jar gt-shapefile-12-SNAPSHOT.jargt-shapefile-ng-9.0-M0.jargt-shapefile-renderer-9.0-M0.jarThis is all expected, gt-shapefile replaces both shapefile and shapefile-ng. Shapefile renderer optimisations have been merged into ht-renderer.gt-transform-12-SNAPSHOT.jar
This is one of the few examples of uDig functionality migrating to GeoTools.itext-2.1.7.jarI thought we got this as a OSGi bundle now?json-20090211.jar json-simple-1.1.jarjson-simple-1.1.jarNot sure what json-20090211.jar is - probably the jar you were missing?jt-jiffle-language-0.2.1.jar jt-jiffle-language-0.2.1.jarjt-jiffleop-0.2.0.jarjt-rangelookup-1.3.0.jar jt-rangelookup-1.3.1.jarI am unfamiliar with this lot, but am aware of some work being done on the ImageIO pipeline - perhaps that is what jt-jiffleop is about?picocontainer-1.2.jar picocontainer-1.2.jar
I should probably drop picocontainer as the project is pretty dead.postgresql-8.4-701.jdbc3.jar postgresql-8.4-701.jdbc3.jarscala-library-2.10.0.jarAssume it followed scala in as a transitive dependency from geoscript.scannotation-1.0.2.jar scannotation-1.0.2.jarslf4j-api-1.5.6.jar slf4j-api-1.5.6.jarslf4j-log4j12-1.5.6.jar slf4j-log4j12-1.5.6.jarsqlite-jdbc-spatialite-3.7.2-2.4.jar sqlite-jdbc-3.7.2.jarsqlite-jdbc-spatialite-3.7.2-2.4.jarstringtemplate-3.2.1.jar stringtemplate-3.2.1.jarvecmath-1.3.2.jar vecmath-1.3.2.jarws-commons-util-1.0.1.jar ws-commons-util-1.0.1.jarxml-apis-1.3.04.jarxml-apis-xerces-2.7.1.jarEither GeoTools is using system XML parser, or we are picking up xerces as a transitive dependency?xml-commons-resolver-1.2.jarNot sure what that one is about.xmlrpc-client-3.0.jar xmlrpc-client-3.0.jarxmlrpc-common-3.0.jar xmlrpc-common-3.0.jarxpp3-1.1.3.4.O.jarxpp3_min-1.1.4c.jar xpp3_min-1.1.4c.jarWonder if we need two copies of xpp3? This will be an XML pull parser of some sort.Jody
_______________________________________________
udig-dev mailing list
udig-dev@xxxxxxxxxxxxxxxx
https://locationtech.org/mailman/listinfo/udig-dev