API Baseline are intended to help you maintain plugins that others can use. The API Tools help you create compatible API versions. Follow the link that Sumit Singh posted to get an explanation on how to use them.
The Problem:
- You create your plugin and release version 1 to the public.
- Millions of people will use your plugin and create their own code that depends on the API of your plugin.
- You release version 2 to the public. By mistake you change the API of your plugin.
- Millions of people update to the new version and have to adapt their code. Thousands of programs fail. People are sad.
The Solution:
- You create your plugin, annotate its API and release version 1 to the public.
- Millions of people will use your plugin and create their own code that depends on the API of your plugin.
- You declare version 1 of your plugin to be the API-Baseline that your code changes are automatically compared against. Any break in the API is presented to you before you release your plugin or run your tests. You release version 2 without any API changes.
- Millions of people can update your plugin in their application, because the new plugin release is binary compatible to the previous one.
- You declare version 2 of your plugin ....
Summary
If you develop a plugin just for your personal use and are not interested to maintain a compatible API, you can follow the advices to disable the warnings.
When you develop plugins for a community, e. g. the eclipse plugins themselves, it is essential that you keep API incompatibilities to a minimum. Then you will follow the advice and set the baseline to 4.2 when you develop for 4.3. The API tools will help you make 4.3 an enjoyment for all current 4.2 users.
Please note, that the API Tools are for the developers of the plugins that will be used by others. They are not addressed at the users of those plugins.