Details
-
Bug
-
Status: Resolved
-
Trivial
-
Resolution: Won't Fix
-
None
-
None
Description
the wicket pom has junit marked as a "compile" dependency. This really isn't necessary, and isn't desired as this will cause wicket webapps to package junit in the war file.
<dependency> <groupId>junit</groupId> <artifactId>junit</artifactId> <version>3.8.1</version> <type>jar</type> <scope>compile</scope> </dependency>
Wicket provides the WicketTester code for projects, but junit should either be marked as "provided" or "optional" to get around this. Another option would be to create a "wicket-tester" module so that users would have to explicitly add that dependency to use this junit dependency.