Jody Garnett a écrit : > Martin Desruisseaux wrote: >> Thats fine for me. Maybe GeoTools doesn't need to be always >> compilable against the latest GeoAPI SVN, as long as it compiles >> against the latest snapshot deployed on the maven repository. >> > You are correct Martin; I was not even going to annoy the geotools > list with this problem until we had sorted it out > on the geoapi mailing list and deployed a snapshot etc... I should probably have subscribe to the GeoAPI mailing list, to be inform that building latest commit of GeoAPI could cause a build error on other projects. I'm fine with the fact that Geotools could sometimes not build with the latest version of GeoAPI trunk, as long as the jar in the repository does.
Cédric >> I believe that Jody wanted to avoid the duplication of a Function >> interface, which is a fine goal in my opinion (if the same interface >> can work for both Expression and Symbol Encoding, maybe with >> sub-interfaces to be introduced). Lets the discussion go on on GeoAPI >> and suggest peoples to not expect a GeoTools alignment until the >> experiments seetle down. I admit that we have lacked communication. >> >> Martin >> > > ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
