[ 
https://issues.apache.org/jira/browse/CONNECTORS-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13068263#comment-13068263
 ] 

Karl Wright commented on CONNECTORS-223:
----------------------------------------

bq. Per default, maven also runs the tests in a separate process.

So does it start the process, run all the tests, and shut the process down?  Or 
does it start a process for each test?

bq. The execution procedure is sequential. Each tests runs to the whole 
lifecycle, before an other test starts.

Ok, that's a relief.

Other than trying to run these tests myself under maven, I can't think of any 
other way to proceed other than to ask you to figure out a way to get at the 
manifoldcf.log output for the test that fails.  The timeout is happening 
because the crawl it sets up is never finishing.  This could well be due to 
some static objects hanging around from one cycle to the next, but I'm never 
going to be able to tell without some work.  I would have thought using ant 
with fork="false" would exercise the same path, but clearly Maven is doing 
something different from that.

Maybe the best way forward is to give me detailed instructions on how to set 
maven up in the way you have it, so I can debug at length.


> Tests in project hierarchy do not adhere to maven conventions
> -------------------------------------------------------------
>
>                 Key: CONNECTORS-223
>                 URL: https://issues.apache.org/jira/browse/CONNECTORS-223
>             Project: ManifoldCF
>          Issue Type: Bug
>          Components: Build
>    Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3
>            Reporter: Karl Wright
>            Assignee: Karl Wright
>             Fix For: ManifoldCF 0.3
>
>         Attachments: CONNECTORS-223.patch, test_reset.patch
>
>
> Maven expects unit tests under .../src/test/java, and root-level project 
> tests under tests/xxx/src/test/java (or equivalent, along with their own 
> pom.xml at tests and tests/xxx).  This is basically compatible with the ant 
> build except in location detail.  The proposal is to move stuff around to 
> make the tests work with maven.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to