backwards-compatibility

We are using clirr( http://clirr.sourceforge.net ) in our project but it looks very outdated. I've tried to search for any alternatives, but they are in the same position: JDiff( http://jdiff.sourceforge.net ) Jar Compare( http://extradata.com/products/jarc/ ) So, I'm looking for community help: how are you solving a problem of checking source and binary compatibility? toniedzwiedz You can also try japicmp , it's a neat project I found recently while trying to perform the same task. Its usage is pretty simple and it comes down to passing it two versions of your library packaged as JARs... for

Closed . This question is opinion-based. It is not currently accepting answers. Learn more . Want to improve this question? Update the question so it can be answered with facts and citations by editing this post . Are there any best practices to keep in mind while designing API's which ensures backward compatibility and new version releases. Any links to articles/blogs is appreciated. You should check out this presentation about API design. It's from Google and pretty good. It also addresses backward compatibility and new releases. How to Design a Good API and Why it Matters keep both running,

Here is the story. I had integrated Google Drive Android SDK (8.1.0) into my app ( AnyCopy ) around three years ago. And I followed the tutorial to set up properly including adding credentials and api key. Everything worked okay. I could backup and restore my data without any problem. Even today it works okay if I download it from Google Play. Recently I have been trying to refactor AnyCopy and integrate the newest Google Drive Android SDK (Google Play Service Version number 12.0.1 )into my app and experiencing a strange error with message java.util.concurrent.ExecutionException: com.google

I'm working on a C# 3.5 assembly that is consumed by many different applications in an enterprise server environment. I would like to add some properties to an existing C# class (not abstract) and maintain backwards compatibility with current clients without recompiling. It’s a strongly named 3.5 assembly. Existing client applications will not be recompiled. Instead we use publisher policy assemblies to re-direct existing clients to the updated version. What are the rules for maintaining this type of class backward compatibility? I'm looking for some set of rules I can validate my code changes

I'm working on an iPhone/iPad/Android app which communicates with a JSON API. The first release of the version of the app is complete, and now additional phases of development are taking place. In the additional phases, the app needs to integrate with a new version of the API and allow the user access to additional features such as new screens or modified behaviour within existing screens. The app does however need to be backwards with previous versions of the API. What is the best practice for tackling such a requirement? I could of could do checks throughout the code: if (APIVersion == 1) {

after reading the apple SDK guide https://developer.apple.com/library/mac/#documentation/developertools/conceptual/cross_development/Overview/overview.html I'm still confused of how to make the mac app backward compatible & how to test them properly I have an app, I run it and tested it on Mountain Lion 10.8 without any problem, however I want to make this app backward compatible so that other users can run it on a mac 10.6 - 10.7 machine. I have an apple developer id and I can download the old versions of 10.7 and 10.6, but the problem is, I have a 2011 macbook air which is currently running

I created a universal app for the iPhone-iPad. I'm only working on the iPhone part at the moment. In the header file for the view controller for the iPhone one, I import the adbanner header and create an adbannerview variable with a matching property. I don't make it in the nib file but rather check at run time if the class exists, if it does, I create an adbanner programmily and then attach the adbannerview variable to it so I can refer to it inside other functions. Everything works on the 4.0 simulator. I also weak linked the iad class. So if I take the same code to an earlier version of

I want to publish a new version of my app that requires Android 4.4. I know I can do this adding the following to the manifest: <uses-sdk android:minSdkVersion="19"/> (19 is the SDK version for Android 4.4 according to this ) But I'd also want people with Android versions older than 4.4 to be able to download an older version of my app. How can I accomplish that, if at all possible? I know iOS does that automatically: If someone has an older iOS version than the required for an app, then an older compatible version of the app id downloaded instead. Does the Google Play Store have a similar