|
If you were logged in you would be able to see more operations.
|
|
|
|
Environment:
|
maven 2.0.7 / Tapestry 4.1.3
|
|
|
mvn jetty:run-war -Dmaven.test.skip generates the following exception.
Everything works fine without the maven.test.skip switch.
org.apache.hivemind.ApplicationRuntimeException: Error: Module tapestry is duplicated! Definition in jar:file:/D:/workspace/app
org.apache.hivemind.impl.StrictErrorHandler.error(StrictErrorHandler.java:39)
|
|
Description
|
mvn jetty:run-war -Dmaven.test.skip generates the following exception.
Everything works fine without the maven.test.skip switch.
org.apache.hivemind.ApplicationRuntimeException: Error: Module tapestry is duplicated! Definition in jar:file:/D:/workspace/app
org.apache.hivemind.impl.StrictErrorHandler.error(StrictErrorHandler.java:39) |
Show » |
|
Bug
Open
Major
mvn parameter maven.test.skip throws exception (Tapestry)
As a workaround the issue seems to occur because difference versions of the tapestry-webframework jar are picked up depending on whether you set the mavent.test.skip property. With the property set 4.1.3 is used, without it 4.1.2 is used. If you run mvn clean in between invocations of jetty:run-war all will work as expected.