I am designing a library, and while I know that I should only make public the classes that I want the client to access, I am having trouble sticking to this best practice. From what I understand, this is best practice. I decided to put a package named internal inside one of the packages in my library to hold the classes that I intend to be package-private, but may end up as public.
The way packages work in Java seems flawed since you cant make a class "parent-package-private", so is there really a "bad practice" when it comes to issues like this?