|[cdt-dev] The Great Managed Build API Tooling Fiasco of 2009|
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?
Team Lead, IBM CDT and RDT