[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cdt-dev] The Great Managed Build API Tooling Fiasco of 2009
|
I agree. We cannot turn it on until we clean it up and this would break some API, so we should leave it till 7.0.
Doug Schaefer wrote:
My only suggestion, don't turn it on for these plugins. It's these
plugins that will make the next release of CDT be 7.0.
Doug.
On Mon, 2009-04-20 at 21:20 -0400, Chris Recoskie wrote:
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
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
