New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[JBLOGGING-184] Make module interfaces accessible in module mode #102
Conversation
(Updated to change |
Also, confirming that using these new methods does indeed fix the above class of errors. |
Ping @jamezp - any thoughts/objections/insights? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry for the delay. This makes sense to me. The only thing I wonder is if we want to add a version to the @Deprecated
annotations and adding the forRemoval = true
.
*/ | ||
@Deprecated |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we want this to be forRemoval = true
and add a since
version?
Sure, that's reasonable. |
How do you prefer it to be formatted? I could do |
It doesn't matter much to me TBH. 3.6 seems fine with me to keep it short, but I'm fine with the long version too. |
Done. I went with the shorter "3.6" option. |
Avoids errors in modular environments.
An example error is: