Community
Participate
Working Groups
I currently see an API baseline error in org.eclipse.core.jobs on the MANIFEST.MF The minor version should be incremented in version 3.10.500, since new APIs have been added since version 3.10.400 But the information which API has been added is missing. I suggest to add this information to the error message otherwise the error analysis for other than the author is really hard. This will also be very useful as soon as Gerrit checks for such errors.
Vikas, could you add this information? I guess this will also make your life easier for future API tools support.
If you click at the error on manifest page, you would see a list of compatible changes - similar to https://bugs.eclipse.org/bugs/attachment.cgi?id=278934
(In reply to Vikas Chandra from comment #2) > If you click at the error on manifest page, you would see a list of > compatible changes - similar to > https://bugs.eclipse.org/bugs/attachment.cgi?id=278934 Lars, does this work for you?
(In reply to Vikas Chandra from comment #3) > (In reply to Vikas Chandra from comment #2) > > If you click at the error on manifest page, you would see a list of > > compatible changes - similar to > > https://bugs.eclipse.org/bugs/attachment.cgi?id=278934 > > Lars, does this work for you? Yes for the IDE. Will we see these also on the command line?
(In reply to Lars Vogel from comment #4) > (In reply to Vikas Chandra from comment #3) > > (In reply to Vikas Chandra from comment #2) > > > If you click at the error on manifest page, you would see a list of > > > compatible changes - similar to > > > https://bugs.eclipse.org/bugs/attachment.cgi?id=278934 > > > > Lars, does this work for you? > > Yes for the IDE. Will we see these also on the command line? This information is there as getAdditionalProposalInfo from the version resolution which in turn returns from marker.getAttribute(IApiMarkerConstants.VERSION_NUMBERING_ATTR_DESCRIPTION, null).
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.
