Fix Non public parameter support #911
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@DirkyJerky |
|
Sorry, but we aren't going to accept this pull request. We don't want tests to pass in some environments where there isn't a security manager (for example, when you run tests from an IDE) and fail in environments where there may be a security manager (for example, a continuous build). Fields, classes and methods annotated with JUnit annotations need to be public. |
hdpe
added a commit
to hdpe/jum
that referenced
this pull request
Jan 4, 2015
The "JUnit way" is to only inject public fields - see e.g. junit-team/junit4#911 (comment).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Maybe?
From #737