Eclipse Community Forums: Plugin Development Environment (PDE) » PDE/API Tools: compare with API baseline

Help

Home

Home » Eclipse Projects » Plugin Development Environment (PDE) » PDE/API Tools: compare with API baseline

Show: Today's Messages :: Show Polls :: Message Navigator

PDE/API Tools: compare with API baseline [message #605760]

Tue, 11 May 2010 10:51

Tristan de Ines

Messages: 4
Registered: July 2009

Junior Member

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="c:\TEMP\BCPluginNew"
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.

Report message to a moderator

Re: PDE/API Tools: compare with API baseline [message #605822 is a reply to message #605760]

Wed, 19 May 2010 15:42

Olivier Thomann

Messages: 518
Registered: July 2009

Senior Member

This should work. If you could give me access to your configuration for the ant task, I should be able to let you know what is not working.

What is wrong with the default baseline approach ? "Compare With... API Baseline" should give you the same answer as doing a build with the default baseline set to the baseline you are comparing with.

I would need more details about your configuration to help you. Something seems wrong with your setup.

Olivier

Report message to a moderator

Previous Topic:	Writing a Custom SSL TrustManager for Eclipse
Next Topic:	Re: Eclipse 3.5, Can't Bundle JRE with Product Export

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Apr 19 08:39:15 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter