Scala Backward Compatibility

Question

What changes or code evolution break backward compatibility (mainly binary compatibility)? Is it fully specified anywhere?

I checked the Scala language specification, but didn't see any section on the matter like Java Language Specification Ch. 13 Binary Compatibility.

Please refer to the specific version jumps you are referring to for future reference. — Raphael, Jun 06 '11 at 09:50
@Raphael, my question wasn't specific to the Scala library. It was about what changes can I do to my own code that break compatibility. — notnoop, Jun 06 '11 at 17:20

score 5 · Accepted Answer · edited Jun 05 '11 at 17:57

5

According to the mailing list, the spec documenting detailing backward compatibility issues does not yet exist but is in the works.

For current status and oulook of binary compatibility (mainly of the scala library), see Martin's message to scala-user mailing list.

For a migration manager preview, see this page http://typesafe.com/technology/migration-manager.

edited Jun 05 '11 at 17:57

notnoop

58,763
21
123
144

answered Jun 05 '11 at 16:27

huynhjl

41,520
14
105
158

score 1 · Answer 2 · answered Apr 09 '16 at 13:27

I've added support for Scala to the japi-compliance-checker tool (1.6 version). So now you can identify breaking changes in your code automatically. The tool is available here: https://github.com/lvc/japi-compliance-checker

Sample usage:

japi-compliance-checker OLD.jar NEW.jar

Also I've created a page with analysis reports for Scala versions evolution generated by this tool as an example: http://abi-laboratory.pro/java/tracker/timeline/scala/

Scala Backward Compatibility

2 Answers2

Linked