[cdt-dev] non-API breaking change required for 6.0 branch to fix a bug

[Alena Laskavaia <elaskavaia.cdt@xxxxxxxxx>]

Customer wants up to fix a bug about multiple breakpoints support
(https://bugs.eclipse.org/bugs/show_bug.cgi?id=221844),
in exiting product which is based on CDT 6.0 (and 5.0). To fix this I
have to add a setter method
into MIBreakpoint class to set a line number (which is non breaking API change).
Any objections if I do it on branches (well on trunk too)? I should
not cause any breakage for anybody because the
only danger is if somebody would extend the class and add a method
with the same name, but people cannot do because field is package
private so they cannot create a setter for it anyway.