FluentLenium/FluentLenium — pull request #43 by jroper (2012-08-26 20:00:14+00:00)
Title: Switched to using junit-dep

Not sure if you're aware, but junit is evil, it bundles its dependent libraries, eg hamcrest, into its own jar. This creates classloader hell if some other library depends on a different version of hamcrest.

junit-dep on the other hand doesn't bundle its dependencies, but rather has a proper pom.xml file to declare its dependencies so they are brought in transitively.

I saw that you had junit-dep marked as provided scope. Maybe this was to work around the issue, because in maven 3 it stops it from being transitively brought into projects? Using junit-dep I think is a better solution to the problem.