Skip to content
This repository has been archived by the owner on Nov 5, 2018. It is now read-only.

Determine visibility for implementating classes #18

Closed
GoogleCodeExporter opened this issue Mar 14, 2015 · 1 comment
Closed

Determine visibility for implementating classes #18

GoogleCodeExporter opened this issue Mar 14, 2015 · 1 comment

Comments

@GoogleCodeExporter
Copy link

Determine if visibility should be reduced for "catalog" implementations (except 
for factory methods). For example, Braillo200Embosser has a public constructor, 
but should really only be called by its Provider. Therefore, package visibility 
should suffice.

Original issue reported on code.google.com by joel.hak...@mtm.se on 21 Dec 2010 at 8:46

@GoogleCodeExporter
Copy link
Author

Most of this should be resolved in the process of making braille utils OSGi 
compatible.

Original comment by joel.hak...@mtm.se on 16 Oct 2014 at 6:54

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants