On 14/11/14 21:08, David ‘Bombe’ Roden wrote: > Hey there, > > so, I was writing a unit test for Fred and I was wondering which version of > JUnit 4 we are using. > > If we already have decided which JUnit version to use we should really > document that somewhere in the source tree, e.g. in README.building.md. > > If we have not yet decided on a version of JUnit 4 (except for “some version > of JUnit 4”) I would like to recommend version 4.11. Reasons include, but are > not limited to: > > - It’s the latest non-beta version. > - It comes in a single variety only; previous versions come in a “junit” and > a “junit-dep” package which, when used together with the Hamcrest matchers, > caused lots of confusion because depending on the JUnit version one or both > packages contained a copy of the matchers. It would be nice if it worked out of the box on debian without having to install third party jars. Historically lots of devs have used debian, and IMHO several still do. > Also, I would like to add two more packages as dependencies for our tests: > > - The aforementioned Hamcrest matchers (version 1.3 of the hamcrest-all > package) which are immensely valuable for writing clear tests. > - The wonderful mockito library which allows to mock dependency objects > during testing. I have not used later versions than 1.9.5 but the changelog > does not imply that more recent versions should pose any problems. Are these available as official packages on common distros?
Anything that is only available unofficially is effectively adding a (build-) dependency on Maven. Doing so would solve a lot of problems, but there are fundamental build security issues with Maven that are hard to resolve efficiently. Official distribution packages don't use Maven - they convert to ant build files and build separately.
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Devl mailing list Devl@freenetproject.org https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
