Justin Deoliveira wrote: > If we want forwards compatibility like this the easiest thing to do (afaik) > is to backport the new fields to the various config objects on trunk back > to 2.0.x, of course leaving them unused. And also tell xstream to ignore > them on serializatsion. Unfortunately it won't listen to ignoring them on > deserialization which is why they are needed in the first place.
For me with my user hat on I don't think backward compatibility is really needed. The important thing is that people know that there is no guarantee that there will be any. Probably a statement on the "migrating" doc page will be enough, i.e. http://docs.geoserver.org/stable/en/user/datadirectory/migrating.html Regards, Miles ___________________________________________________________________________ Australian Antarctic Division - Commonwealth of Australia IMPORTANT: This transmission is intended for the addressee only. If you are not the intended recipient, you are notified that use or dissemination of this communication is strictly prohibited by Commonwealth law. If you have received this transmission in error, please notify the sender immediately by e-mail or by telephoning +61 3 6232 3209 and DELETE the message. Visit our web site at http://www.antarctica.gov.au/ ___________________________________________________________________________ ------------------------------------------------------------------------------ Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
