toggle quoted messageShow quoted text
So… let me ask this question… can we actually realistically carry out this distinction before we have the
necessary tooling in hand?
On Oct 29, 2014, at 10:26 AM, Colin Dixon <colin@...
I think we have three threads going on:
1.) Not everyone likes the term Legacy and I actually agree with Chris that Stable is a lot better. The definition actually does match that since it says those APIs should remain the same (stable) throughout the release. Supported says bad things about the
other APIs that I don't think we want to imply. My vote would be for Stable.
2.) We desperately need tools to help us track APIs, who's using them (across projects) and what state they're in. This is true and I'd love to see us develop some of these tools, perhaps as part of existing/new releng projects.
3.) In the shorter run, I'd really like to see somebody write up simple documentation/tutorials about how people can limit the visibility of their APIs both in pom files and with java keywords.
Exploring using annotations seems like another great idea, but with the exception of @Deprecated, do any of them show up in a visible way for developers? It seems like we'd need a corresponding Eclipse plugin to help most of our developers understand when they
were using different kinds of APIs and the expectations they come with.
TSC mailing list