Desmond, There are a few tests that are unfortunately timing-specific (i.e. they are testing timeouts) and sometimes for some reason that I can't explain they fail (if anyone knows how to fix them, feel free to recommend a solution). If you try compiling again it will probably work.
If it doesn't, execute maven with the following: mvn -Dmaven.test.skip=true package install (where package and install are the goals you are executing) That will skip all of the tests in the odd event that the one test won't work. -Scott On 10/1/07, Desmond Stewart <[EMAIL PROTECTED]> wrote: > > Hi I'm new to the list. We are looking at deploying CAS at Alcorn State > University. I have a general question. I'm not a Java developer and the > curve is kinda wild. I'm getting a build error with maven at the test. > Message: > > > Results : > > Failed tests: > testTicketIsExpiredByTime( > org.jasig.cas.ticket.support.MultiTimeUseOrTimeoutEx > pirationPolicyTests) > > Tests run: 392, Failures: 1, Errors: 0, Skipped: 0 > > [INFO] > ------------------------------------------------------------------------ > [ERROR] BUILD FAILURE > [INFO] > ------------------------------------------------------------------------ > [INFO] There are test failures. > [INFO] > ------------------------------------------------------------------------ > [INFO] Trace > org.apache.maven.BuildFailureException: There are test failures. > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa > ultLifecycleExecutor.java:560) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi > fecycle(DefaultLifecycleExecutor.java:480) > at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal > (Defau > ltLifecycleExecutor.java:459) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan > dleFailures(DefaultLifecycleExecutor.java:311) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen > ts(DefaultLifecycleExecutor.java:278) > at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute > (DefaultLi > fecycleExecutor.java:143) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke > (NativeMethodAccessorImpl. > java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke > (DelegatingMethodAcces > sorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > 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) > Caused by: org.apache.maven.plugin.MojoFailureException: There are test > failures > . > at org.apache.maven.plugin.surefire.SurefirePlugin.execute > (SurefirePlugi > n.java:425) > at org.apache.maven.plugin.DefaultPluginManager.executeMojo > (DefaultPlugi > nManager.java:443) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa > ultLifecycleExecutor.java:539) > ... 16 more > > > > I'm lost.. I just stop compilling. I've done it before. The only thing > different is the ip address to the ldap server. That's why I complied > again. > > > > Any ideas > > > > Desmond Stewart > > _______________________________________________ > Yale CAS mailing list > [email protected] > http://tp.its.yale.edu/mailman/listinfo/cas > > -- -Scott Battaglia LinkedIn: http://www.linkedin.com/in/scottbattaglia
_______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
