Community
Participate
Working Groups
When API tooling reports that a minor/major version change is needed, it would be very helpful if the manifest message included at least one of the API changes that causes the verdict. Too often I do not believe the verdict, dismiss it as an API tooling error and just filter it out. Clearly, either the tool or I am wrong, but without the example it is hard to tell. It would also help if the API tooling messages included references to the Java API evolution document in which the problems and rationale are explained in detail.
You've described two separate feature requests. I'm refocusing this bug on the first issue as it is better scoped and might be something worth considering for 4.5.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
