@ -138,16 +138,14 @@
depend on JUnit 4.11 (<literal > junit:junit</literal> ), TestNG 6.5.2
depend on JUnit 4.11 (<literal > junit:junit</literal> ), TestNG 6.5.2
(<literal > org.testng:testng</literal> ), and Hamcrest Core 1.3
(<literal > org.testng:testng</literal> ), and Hamcrest Core 1.3
(<literal > org.hamcrest:hamcrest-core</literal> ). Each of these
(<literal > org.hamcrest:hamcrest-core</literal> ). Each of these
dependencies is declared as an <emphasis > optional</emphasis> dependency
dependencies is declared as an <emphasis > optional</emphasis> dependency in
in the Maven POM. Furthermore, it is important to note that the JUnit
the Maven POM. Furthermore, it is important to note that the JUnit team
team has stopped inlining Hamcrest Core within the
has stopped inlining Hamcrest Core within the
<literal > junit:junit</literal> Maven artifact as of JUnit 4.11. Thus, if
<literal > junit:junit</literal> Maven artifact as of JUnit 4.11. Hamcrest
your existing JUnit-based tests make use of Hamcrest matchers that were
Core is now a <emphasis > required</emphasis> transitive dependency of
previously available directly within the <literal > junit:junit</literal>
<literal > junit</literal> , and users may therefore need to remove any
JAR, you will now need to explicitly declare a dependency on
exclusions on <literal > hamcrest-core</literal> that they had previously
<literal > org.hamcrest:hamcrest-core</literal> ,
configured for their build.</para>
<literal > org.hamcrest:hamcrest-library</literal> , or
<literal > org.hamcrest:hamcrest-all</literal> .</para>
</section>
</section>
<section xml:id= "migration-3.2-changes" >
<section xml:id= "migration-3.2-changes" >