Details

    • Type: Task
    • Status: Resolved
    • Priority: Major
    • Resolution: Complete
    • Affects Version/s: 3.2 M2
    • Fix Version/s: 3.2 GA
    • Component/s: [Build], Test
    • Labels:
      None
    • Last commented by a User:
      false

      Description

      Status Quo

      The JUnit team recently released JUnit 4.11.

      Excerpt from the JUnit 4.11 Release Notes

      The following information is applicable to the Spring Framework build, especially with regard to junit:junit vs. junit:junit-dep and Hamcrest Maven dependencies.

      Maven artifacts

      Up until now there were two Maven artifacts for JUnit: junit:junit-dep and junit:junit. From a Maven point-of-view only the former made sense because it did not contain the Hamcrest classes but declared a dependency to the Hamcrest Maven artifact. The latter included the Hamcrest classes which was very un-Maven-like.

      From this release on, you should use junit:junit which will be what junit:junit-dep used to. If you still reference junit:junit-dep, Maven will automatically relocate you to the new junit:junit and issue a warning for you to fix.

      Deliverables

      1. Upgrade the dependency on JUnit in the spring-test module from 4.10 to 4.11.
      2. Update the entire Gradle build to use JUnit 4.11 instead of the 4.11 snapshot build currently in use.
      3. Update the changelog.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                sbrannen Sam Brannen
                Reporter:
                sbrannen Sam Brannen
                Last updater:
                Juergen Hoeller
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Days since last comment:
                  5 years, 25 weeks, 4 days ago