| RE: [cdt-dev] The Great Managed Build API Tooling Fiasco of 2009 |
This seems to have worked out, so unless there are any objections I'm going to look at checking in changes to enable this. There have not been many API changes in MBS in this release, so there were not many API errors to fix. Mostly missing @since tags.
One thing to note is that the plugin versions will be raised to 5.1.0. I see they are currently at 5.0.100 for some reason.
===========================
Chris Recoskie
Team Lead, IBM CDT and RDT
IBM Toronto
"Schorn, Markus" <Markus.Schorn@xxxxxxxxxxxxx>
Sent by: cdt-dev-bounces@xxxxxxxxxxx 04/21/2009 04:15 AM
|
|
Folks,
I've been looking at turning on the API tooling on the MBS plugins. However, I've hit a big snag in that many of the internal packages are not named correctly (using org.eclipse.cdt.managedbuilder.internal.* instead of org.eclipse.cdt.internal.managedbuilder.*) This causes the API tooling to think that these packages are public, and it reports gazillions of errors on them that should not be considered errors..
My first instinct was to perhaps refactor these packages to use the right naming convention, but then we lose the CVS history on them all, and this affects a lot of classes :-(
Setting up manual exclusions would be a tedious nightmare, and would end up being an ongoing process that continues whenver someone makes a change to the internals.
I've looked to see if there is a way to add additonal rules as to how internal packages are named, but I can't seem to find this anywhere.
Does anyone have suggestions/opinions?
===========================
Chris Recoskie
Team Lead, IBM CDT and RDT
IBM Toronto_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
