You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think modules can only be as granular as packages, and everything in that package is accessible via reflection. So, if you want something not exposed, even by reflection, you have to put it in a separate package in a separate module and define the relationships between the modules in your module-info.java. In the other module, it will probably have to be more visible (public) so you can use it across the traditional package boundaries.
mdn
locked and limited conversation to collaborators
Dec 30, 2024
queengooborg
changed the title
I think modules can only be as granular as packages, and everything in that package is accessible via reflection. So, if you want something not exposed, even by reflection, you have to put it in a separate package in a separate module and define the relationships between the modules in your module-info.java. In the other module, it will probably have to be more visible (public) so you can use it across the traditional package boundaries.
[Spam]
Dec 31, 2024
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I think modules can only be as granular as packages, and everything in that package is accessible via reflection. So, if you want something not exposed, even by reflection, you have to put it in a separate package in a separate module and define the relationships between the modules in your
module-info.java
. In the other module, it will probably have to be more visible (public) so you can use it across the traditional package boundaries.Originally posted by @ctubbsii in apache/accumulo-access#81 (comment)
The text was updated successfully, but these errors were encountered: