This post originated from an RSS feed registered with Java Buzz
by Joe Shelby.
Original Post: Evolving an API without losing compatibility
Feed Title: Joe's Java Jottings
Feed URL: http://www.blog-city.com/bc/
Feed Description: Notes, observations, and occasional other stuff on Java, with concentrations on Swing, XML, and the Semantic (Object) Web.
http://www.eclipse.org/eclipse/development/java-api-evolution.html
An article from the Eclipse team on maintaining backwards compatibility with library methods and classes. Helps make clear what is and isn't a "public API", addressing both compile-time and binary issues.