Breaking changes for 2.0

This issue will encapsulate breaking changes that we’re considering for a future 2.0 release. Things like removing deprecated functionality, removing incorrect classes / methods, changing parts of the design, etc.

These items can go into the 2.0 branch.

To add an item to this list please add a comment.

Current list of 2.0 proposals:

• update extensible and non-extensible Links: models
• Remove methods that were renamed (and deprecated) in 1.1 Links: 256 261 268 280
• Delegate document / property location to MP Config Links: Arch Board 46
• (#240) All getters returning a list or a map MUST return copy of this list/map containing the same items. This list/map CAN be immutable
• (#284) The setters having a list or a map as parameter MUST not use the list/map instance directly (it can be for example an immutable list/map)
• (#345) Removal of the Scopes mode
• (#348) Remove ServerVariables
• (#352) Removed parameter target in Parameters annotation
• (#384) Add SchemaProperty Annotation

[arthurdm]

I agree @jmini - let’s keep an eye out this year for other specs potentially also in this situation (i.e. about to force an umbrella 3.0 version) and target our 2.0 to go along with them. There’s nothing very urgent in 2.0 so far, and we can do a few of the MR builds if needed.

[jmini]

For this point:

Remove methods that were renamed (and deprecated) in 1.1

Add: #261