[
https://issues.apache.org/jira/browse/CONNECTORS-628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13566413#comment-13566413
]
Karl Wright commented on CONNECTORS-628:
----------------------------------------
Yup, looks pretty easy to fix...
> Maven integration tests broken
> ------------------------------
>
> Key: CONNECTORS-628
> URL: https://issues.apache.org/jira/browse/CONNECTORS-628
> Project: ManifoldCF
> Issue Type: Bug
> Components: Build, Tests
> Affects Versions: ManifoldCF 1.0.1
> Reporter: Piergiorgio Lucidi
> Assignee: Piergiorgio Lucidi
> Fix For: ManifoldCF 1.2
>
>
> Trying to execute integration tests using Maven it returns the following
> exception:
> {code}
> Running org.apache.manifoldcf.filesystem_tests.APISanityCombinedHSQLDBIT
> Configuration file successfully read
> 45 [main] INFO org.eclipse.jetty.server.Server - jetty-7.5.4.v20111024
> 90 [main] WARN org.eclipse.jetty.webapp.WebInfConfiguration - Web application
> not found ../../framework/build/war-proprietary/mcf-combined-service.war
> 91 [main] WARN org.eclipse.jetty.webapp.WebAppContext - Failed startup of
> context
> o.e.j.w.WebAppContext{/mcf,null},../../framework/build/war-proprietary/mcf-combined-service.war
> java.io.FileNotFoundException:
> ../../framework/build/war-proprietary/mcf-combined-service.war
> at
> org.eclipse.jetty.webapp.WebInfConfiguration.unpack(WebInfConfiguration.java:479)
> at
> org.eclipse.jetty.webapp.WebInfConfiguration.preConfigure(WebInfConfiguration.java:52)
> at
> org.eclipse.jetty.webapp.WebAppContext.preConfigure(WebAppContext.java:417)
> at
> org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:453)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:59)
> at
> org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:224)
> at
> org.eclipse.jetty.server.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:167)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:59)
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:89)
> at org.eclipse.jetty.server.Server.doStart(Server.java:261)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:59)
> at
> org.apache.manifoldcf.crawler.tests.ManifoldCFInstance.start(ManifoldCFInstance.java:519)
> at
> org.apache.manifoldcf.crawler.tests.BaseITHSQLDB.setUp(BaseITHSQLDB.java:214)
> 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:597)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:27)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:236)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:134)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:113)
> 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:597)
> at
> org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
> at
> org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
> at
> org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:103)
> at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74)
> ....
> ...
> ..
> .....
> .....
> Results :
> Tests in error:
>
> sanityCheck(org.apache.manifoldcf.filesystem_tests.APISanityCombinedHSQLDBIT):
> API http error; expected 201, saw 503: <html>(..)
> Tests run: 9, Failures: 0, Errors: 1, Skipped: 0
> {code}
> Probably this is due to the combined project that doesn't have a pom.xml.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
