Jochen, Hamcrest 1.3 used to be pulled in by JUnit, but it isn't pulled in by JUnit5. When I converted all the tests to JUnit5 syntax and dropped the JUnit4 bridge then I needed to pull in hamcrest explicitly. I went with 1.3 to match the rest of the code base.
Tim On Mon, Feb 1, 2021 at 12:59 AM Jochen Wiedmann <[email protected]> wrote: > On Mon, Jan 25, 2021 at 10:06 PM Tim Perry <[email protected]> wrote: > > > > Is it okay to import hamcrest to use in the tests? > > > > <dependency> > > <groupId>org.hamcrest</groupId> > > <artifactId>hamcrest</artifactId> > > <version>2.2</version> > > <scope>test</scope> > > </dependency> > > Isn't that pulled in automatically via junit? See, for example, the > Pom in https://search.maven.org/artifact/junit/junit/4.13.1/jar. > > Jochen > > > > -- > > Look, that's why there's rules, understand? So that you think before > you break 'em. > > -- (Terry Pratchett, Thief of Time) >
