| [pde-dev] API Tools - Comparing API Baselines |
Hi,
I posted this question on the Eclipse PDE forum: http://www.eclipse.org/forums/index.php?t=msg&th=167976&start=0& But as the API Tools are a relatively new feature still in development, and the mailing list seems to receive more exposure to the people who know the internals (pun intended), I hope you don't mind if I draw some attention to it here: --- Hi, I'm experimenting with the Eclipse API Tools and for that purpose I have created two plug-in projects in my workspace. The second is a variation of the "original" first project with Java binary compatibility problems introduced. If I export the first project as deployable plug-in and set it as the default baseline, the projects are recompiled and the compatibility problems are reported correctly in the second project. Unfortunately this is the only way I'm currently able to use API Tools. As far as I know you should also be able to compare a plug-in project with any baseline using the context-menu: "Compare with -> API Baseline". If I try this comparing the second project with the first project baseline, I always get "No changes have been found" in the API Tooling view. A third way of using API Tools are the ant-tasks. I exported both projects as deployable plug-ins and tried to compare them with the following ant-task: <target name="run"> <apitooling.analysis baseline="c:\TEMP\BCPluginOld" profile="" report="c:\TEMP\report" debug="true" /> </target> This produces the following output on the console, but it doesn't generate a report. After execution there is no "report" directory in c:\TEMP: run: [apitooling.analysis] reference : c:\TEMP\BCPluginOld [apitooling.analysis] baseline to compare : c:\TEMP\BCPluginNew [apitooling.analysis] report location : c:\TEMP\report [apitooling.analysis] No filter store [apitooling.analysis] No exclude list location [apitooling.analysis] Preparation of baseline installation : 2ms [apitooling.analysis] Creation of both baselines : 45ms [apitooling.analysis] Total number of components in current baseline :2 [apitooling.analysis] Total number of api tools components in current baseline :1 [apitooling.analysis] Details: [apitooling.analysis] BCPlugin [apitooling.analysis] ============================================================ ================== [apitooling.analysis] Total number of non-api tools components in current baseline :0 [apitooling.analysis] Details: [apitooling.analysis] API tools verification check : 115ms [apitooling.analysis] Cleanup : 2ms BUILD SUCCESSFUL Some leads on what I'm doing wrong or how to effectively work with API Tools without taking the default baseline approach would be greatly appreciated.
|