-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Allow @Rule annotation on non-public fields #31
Comments
I agree. It is a strange requirement/limitation. |
I'm voting this up, but only because I've gotten used to the DI/Spring (and other frameworks) way of 'peering' into the private internals of a class and perusing the members therein. On the other hand, I can see how sticking to |
I agree, too. In the mailing list, there is already a working patch for this: |
Tests that grab private members reflectively can fail when run under security managers and runtimes that prevent such access, so we push test writers to make their tests most generally useful. Since the only "client" of a JUnit test class is the framework itself, I haven't seen a big loss in design from this requirement. Please bring this up on junit@yahoogroups.com if you strongly disagree, so we can hear from both sides. Thanks. |
Fix SL4J-EXT manifest, duplicate bundle name with SL4J-LOG4J
I really don't see why fields with a @rule annotations must be public and it's quite easy to fix...
The text was updated successfully, but these errors were encountered: