forked from junit-team/junit4
-
Notifications
You must be signed in to change notification settings - Fork 0
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
sync to latest #1
Merged
Merged
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
Updated answer as discussed on JUnit's Yahoo! Group: If you are using JDK 1.3 or higher, you can use reflection to subvert the access control mechanism with the aid of the <a href="http://sourceforge.net/projects/privaccessor/">PrivilegedAccessor</a>. For details on how to use it, read <a href="http://www.onjava.com/pub/a/onjava/2003/11/12/reflection.html">this article</a>. If you are using JDK 1.6 or higher and you annotate your tests with @test, you can use <a href="http://dp4j.com">Dp4j</a> to inject reflection in your test methods. For details on how to use it, see <a href="http://dp4j.com/testscript">this test script</a>.
included logo image file, created suitable css class, adapted wording a bit
included amex logo as new main sponsor
This reverts commit 720ee19.
This is needed because classes annotated with @FixMethodOrder will not be reordered or sorted, so having both annotations is a contradiction. - Add AnnotationValidator to fail if class annotated with @FixMethodOrder - Annotate OrderWith with @ValidateWith(OrderWithValidator.class) - Add tests for the new validator
We forgot to add this changes to the release notes. Fixes #1645.
We are using Maven 3.1.1 which by default uses HTTP instead of HTTPS for resolving artifacts from Maven Central. Maven Central recently discontinued HTTP support. Therefore the build on Travis started failing. By using an HTTPS mirror of Maven Central the build on Travis will work again. I chose Google's mirror because Travis uses this mirror by default, too. I did not upgrade to a new version of Maven because there is no newer version with Java 5 support and it should be possible to build JUnit 4 with Java 5 so that we can easily ensure that it works with Java 5.
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.
No description provided.