Hi all, As per my discussion with Martin in IRC yesterday I looked at making 2.3.x compile against geoapi trunk. However, its more work then I initially thought, its not just the additional method on Expression itself, there are a number of over changes:
1. The FeatureId interface has been totally changed 2. Filter.EXCLUDE, Filter.INCLUDE, NilExpression added 3. Visitor interface has been changed Bottom line I am not comfortable making these changes so close to release. So I really think we need a geoapi branch where we can just deprecate / remove the methods we need to. I would be happy to make the changes for 2.3.1, but for this release I think its a bad idea. -Justin -- Justin Deoliveira [EMAIL PROTECTED] The Open Planning Project http://topp.openplans.org ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
