Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have a library project and I want to limit the public API but I also have some low-level utility classes that are shared among some of the packages. I need these utility classes to be publicly accessible, but I do not want to expose them in the library’s public API.
I thought about doing reflection but it seems a little to messy for this application.
Any help would be appreciated.
Don’t include these classes in the documentation of the API, or document them with a bold warning: This class is for internal use only and is subject to changes or removal in future versions of the API. Don’t use it.
Putting these classes in a
com.foo.bar.internalpackage is also useful.