Eclipse Community Forums: Plugin Development Environment (PDE) » @since and dependencies in API tooling

Help

Home

Home » Eclipse Projects » Plugin Development Environment (PDE) » @since and dependencies in API tooling

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

@since and dependencies in API tooling [message #803490]

Tue, 21 February 2012 12:19

Thorsten Meinl

Messages: 85
Registered: July 2009

Member

Hi all,

I have a question regarding the API tooling checks for @since and bundle
dependencies with versions. Suppose you have a bundle A that depends on
bundle B in version 1.0.0. Now B gets a new type and its version is
increased to 1.1, the new type is flagged with @since 1.1. A now uses
the the new type but still requires B in version 1.0 which is obviously
wrong. I would expect API Tooling to find such errors but it doesn't
seem to work.

Thorsten

Report message to a moderator

Re: @since and dependencies in API tooling [message #803678 is a reply to message #803490]

Tue, 21 February 2012 16:52

Curtis Windatt

Messages: 166
Registered: July 2009

Senior Member

API Tooling does not check your dependencies, it checks that you have not broken API contracts. This is actually more closely related to PDE Core tooling. Such a feature is possible, but it could be very flaky as @since tags are in no way guaranteed to match the bundle version (API Tools encourages this behaviour in APIs, but it is not strictly enforced as there are different version schemes used). The only way to be sure that the dependency range is correct is to have each version of the bundle available to check.

Report message to a moderator

Previous Topic:	ContentAssistant and partitioned documents
Next Topic:	Maven+Tycho build completes successfully, but product does not contain application

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Tue Aug 09 11:52:25 GMT 2022

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter