wicket how to unit test with deployment configuration

in your unit test, don’t use Application

instead use something liket his:

private static class DeploymentApplication extends Application {
public org.apache.wicket.RuntimeConfigurationType getConfigurationType() {
return RuntimeConfigurationType.DEPLOYMENT; // some freaky wicket bug where if you are in DEVELOPMENT you can’t have any duplicate label values [we do TODO get rid of duplicates, then remove this weirdo (inspired by http://www.mkyong.com/wicket/how-to-change-wicket-to-deployment-mode)

centos/redhat 6 nproc thread limit 1024

Looks like they enforced an arbitrary limit of 1000 or 1024 threads in CentOS 6 [it wasn't limited by default in CentOS 5] based on this bug:


And this



For fix see http://stackoverflow.com/a/25813438/32453

ref: http://serverfault.com/q/356962/27813


mvn dependency:copy woe

[INFO] Final Memory: 11M/154M
[INFO] ————————————————————————
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:2.8:copy (default-cli) on project myArtifactId: Either artifact or artifactIt
ems is required -> [Help 1]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException


meant “run it like this instead”
c:\dev\intellijbug\myArtifactId>mvn dependency:copy-dependencies