You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Jean-Baptiste Quenot (JIRA)" <ji...@apache.org> on 2007/06/10 18:36:26 UTC
[jira] Updated: (WICKET-284) Cannot execute tests from within
wicket-parent
[ https://issues.apache.org/jira/browse/WICKET-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Quenot updated WICKET-284:
----------------------------------------
Fix Version/s: (was: trunk)
1.3.0-beta1
> Cannot execute tests from within wicket-parent
> ----------------------------------------------
>
> Key: WICKET-284
> URL: https://issues.apache.org/jira/browse/WICKET-284
> Project: Wicket
> Issue Type: Bug
> Reporter: Jean-Baptiste Quenot
> Assignee: Jean-Baptiste Quenot
> Fix For: 1.3.0-beta1, 2.0 branch (discontinued)
>
>
> {noformat}
> $ cd wicket-1.x/wicket-parent
> $ mvn -Pjdk1.4 test
> ...
> [INFO] ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] There are test failures.
> [INFO] ------------------------------------------------------------------------
> {noformat}
> If you look at wicket-examples/target/surefire-reports/wicket.examples.helloworld.HelloWorldTest.txt (for example), you see that Jetty is not launched from within the right directory (current working directory remains *wicket-parent*):
> {noformat}
> java.io.FileNotFoundException: src/main/webapp
> at org.mortbay.jetty.webapp.WebAppContext.resolveWebApp(WebAppContext.java:896)
> at org.mortbay.jetty.webapp.WebAppContext.getWebInf(WebAppContext.java:746)
> at org.mortbay.jetty.webapp.WebInfConfiguration.configureClassLoader(WebInfConfiguration.java:62)
> at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:453)
> at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:38)
> at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:119)
> at org.mortbay.jetty.Server.doStart(Server.java:210)
> at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:38)
> at nl.openedge.util.jetty.JettyDecorator.setUp(JettyDecorator.java:123)
> at junit.extensions.TestSetup$1.protect(TestSetup.java:18)
> at junit.framework.TestResult.runProtected(TestResult.java:124)
> at junit.extensions.TestSetup.run(TestSetup.java:23)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.apache.maven.surefire.battery.JUnitBattery.executeJUnit(JUnitBattery.java:242)
> at org.apache.maven.surefire.battery.JUnitBattery.execute(JUnitBattery.java:216)
> at org.apache.maven.surefire.Surefire.executeBattery(Surefire.java:215)
> at org.apache.maven.surefire.Surefire.run(Surefire.java:163)
> at org.apache.maven.surefire.Surefire.run(Surefire.java:87)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.apache.maven.surefire.SurefireBooter.runTestsInProcess(SurefireBooter.java:313)
> at org.apache.maven.surefire.SurefireBooter.run(SurefireBooter.java:221)
> at org.apache.maven.test.SurefirePlugin.execute(SurefirePlugin.java:371)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> {noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.