[
https://issues.apache.org/jira/browse/CONNECTORS-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13067837#comment-13067837
]
Karl Wright commented on CONNECTORS-223:
----------------------------------------
I tried to simulate what maven does by changing the ant build's junit
invocation from "fork="true"" to "fork="false"". When I do this without the
patch, I get the same symptom as you see under Maven. With the patch, however,
it works fine.
I think perhaps there is a problem with your testing procedure? I'm going to
commit the patch changes now - could you synch up and try them again under
maven?
r1148443.
> 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
