RE: [eclipse-dev] How to deal with API leakage?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

RE: [eclipse-dev] How to deal with API leakage?

From: "Jeff McAffer" <jeff@xxxxxxxxx>
Date: Thu, 17 Apr 2008 21:55:31 -0400
Delivered-to: eclipse-dev@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/eclipse-dev>
List-help: <mailto:eclipse-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/eclipse-dev>, <mailto:eclipse-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/listinfo/eclipse-dev>, <mailto:eclipse-dev-request@eclipse.org?subject=unsubscribe>
Organization: Code 9
Thread-index: AcigBikbGLuomTedTjC4PYGKqyFpAgA8PYsg

> We found a similar case in debug (before API tooling existed).

Can you point people to the part of API tooling that helps with API leakage.
Seems like it would actually be a good thing to have everyone run if not as
part of the build...

Jeff

References:
- [eclipse-dev] How to deal with API leakage?
  - From: Boris Bokowski
- Re: [eclipse-dev] How to deal with API leakage?
  - From: Darin Wright

Prev by Date: Re: [eclipse-dev] consistent CVS tags for builds?
Next by Date: [eclipse-dev] Eclipse 3.4 shape
Previous by thread: Re: [eclipse-dev] How to deal with API leakage?
Next by thread: [eclipse-dev] Eclipse 3.4 shape
Index(es):
- Date
- Thread

Breadcrumbs