Andrea I am starting up a major (and short term) project on uDig trunk - with a deadline in October. So I cannot afford to have geotools trunk go crazy either. Jesse also wants to demo uDig trunk at FOSS4G which I think agrees with the GeoServer 2.0 timeline? > So, what will it be? PSC, we need a decision. > So as a GeoServer PSC the question for me comes down to exactly what the scope is for 2.6.0 - if it is just a race to get the wicket UI ready in time for demo at FOSS4G in september I am going to be tempted to recommend staying with GeoTools 2.5.0 (yes I understand that this is a bad long term risk management move; and I also understand it would really hurt my above mentioned uDig project). > All things considered, having gt2 trunk go wild scares me more than having to > deal with the occasional issues due to living on trunk but the ability to > release 2.6.0 in time concerns me quite a bit. > This is a very fair concern; and one that is a risk for me on the uDig side - given that uDig is taking trunk seriously I expect to turn up lots of bug fixes around areas of the library that are "new" since GeoTools 2.2 (so raster support; filter and the feature model) and there are known problems with referencing.
Can I ask where in the GeoSever code base the system properties to control the referening module are? I have tried figuring out what to set based on reading javadocs and have come up frustrated. > I've asked on the gt2 channel about what will the 2.6.0 major change be, > hopefully that will shed some light on this last concern. > I am also waiting on that thread; currently my vote is a range of -1..1 inclusive... Jody ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
