> All of the persistence classes currently appear to be public. > I plan to make those that are not called from outside that > package become package scope. These are helper methods > designed to be used internally by the other persistence > classes. Do I really have to deprecate these before changing > or can I short cut this?
For helper functions that were clearly made public in error, I think just reducing the visibility of them is fine. Including a note in the comments/javadoc to make it obvious on the remote chance that there is a problem is probably a good idea. > I'll then review what is left to try and define a more stable API. That brings up a question that's been rattling around in the back of my mind as a result of the API compatibility questions. Should we try to do a focused review of the entire public API and do one big update where we warn developers of potential incompatibilites? Or is it better to just keep trying to chip away at the problem incrementally? I'm not sure we have the resources to do a global review, but figured I'd ask the question. Tom --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
