[eclipse-dev] Re: API Tooling and "component.xml"

[Darin Wright <Darin_Wright@xxxxxxxxxx>]

As part of the migration to API tooling adoption, we have been 
recommending that developers delete their "component.xml" files (if they 
exist). The information in "component.xml" is migrated to javadoc tags in 
API tooling. API tooling does not maintain component.xml files.

However, we are wondering if there is any tooling or teams out there that 
actually use the component.xml files any more? Many of the component.xml 
files are old, stale, or do not even exist - so we would rather see them 
deleted. 

Speak now or forever hold your peace :-)

P.S. Thanks to the early adopters of API tooling who have uncovered a few 
good bugs. Next week's build should be even better.

Thanks,

Darin Wright

> Attention developers,
> 
> PDE's new API Tooling goes live in this week's integration build! Among 
> other things, you will be able to explicitly document your API's with 
> javadoc tags (like @noextend, @noinstantiate, etc.),  discover binary 
> compatibility problems with a previous release, and locate invalid 
@since 
> tags and bundle version numbers.
> 
> A user guide on how to set up and use the tooling can be found on the 
> wiki:
> 
>         http://wiki.eclipse.org/API_Tooling_User_Guide
> 
> We encourage you to try out the new tooling and file any bugs/issues 
under 
> the "PDE / API Tools" bugzilla  component.
> 
> Thanks,
> 
> The PDE API Tooling Team