Hi devs,

I just stumbled across this (again) while upgrading some libraries from 4.2.0 to 4.3.0.

As I got some compile errors caused by the change to require Dictionary<String, ?> instead of just Dictionary for e.g. service registration (which effectively is a change in contract - breaking API - in a minor version update), I had a look into the JavaDoc for Dictionary again and noticed (again) that it had been deprecated for quite some time.

So I have the following questions:

1.) Why breaking compile-time API in a minor version release - at least for Java 1.5+?

2.) If breaking compile-time anyway why not just clean up at the same time (Dictionary -> Map)?

3.) Why is Dictionary still being used in r5 (Map is there since Java 1.2 - should be safe to change)?

I would have expected that new methods get introduced in that minor version update using Map and the other ones marked as deprecated, so that code maintainers have a grace period where they can test new features coming with the new release without having to change other parts of their module.

Thanx for any comments on this.

Cheers,

        Ancoron
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev

Reply via email to