Hello Kevin, we try our best to maintain compatibility from a version to the previous one. Sometimes classes are moving from one package to another which oblige you to update the import path, sometimes API methods are not used any more but we try to keep the old methods by depreciating them and by branching new code from the old methods. Note that when a method which is still in usage for example in 2.0 is deprecated in 2.1, it will be removed in 2.2 (idem for 1.1 / 2.0 / 2.1). If you are using extensions, some of them are relying on external librairies. In this case, you have to take care of the new version of the libraries java archives. They are all available in the "/libraries" directory of the Restlet distribution.
If you are relying on the internal HTTP client and server connectors, I suggest to move to ones provided by extensions such as "net", "httpclient", "jetty", "simple" since these internal connectors are on the way to be stabilized. I've read the changes.log ( http://www.restlet.org/documentation/2.1/jse/changes) and I think the upgrade will be fine. The API is more stable then before. Best regards, Thierry Boileau Will restlet 2.1 be backward compatible with applications developed for 2.0? > Are you following a documented versioning scheme you can point me to, that > states that versions with the same major number are backward compatible? > > We have an app based on 2.0 and I'm wanting to verify that we'll be able to > drop in 2.1.0 when it is ready (and then regression test the app of > course!) > > Thanks... > > > > -- > View this message in context: > http://restlet-discuss.1400322.n2.nabble.com/Restlet-Versioning-Scheme-tp7578345.html > Sent from the Restlet Discuss mailing list archive at Nabble.com. > > ------------------------------------------------------ > > http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=3004066 > ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=3030215
