[
https://issues.apache.org/jira/browse/CONNECTORS-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13065753#comment-13065753
]
Tobias Rübner commented on CONNECTORS-223:
------------------------------------------
Maven strongly depends on conventions.
By default, the Maven Surefire Plugin, which executes the tests, will
automatically include all test classes with the following wildcard patterns:
* "**/Test*.java" - includes all of its subdirectories and all java filenames
that start with "Test".
* "**/*Test.java" - includes all of its subdirectories and all java filenames
that end with "Test".
* "**/*TestCase.java" - includes all of its subdirectories and all java
filenames that end with "TestCase".
Your test class names do not match this convention.
Now we have 2 choices:
* rename the test classes (e.g. mcf-agents Sanity -> SanityTest)
* change the pattern to include the tests (**/Sanity*.java)
> 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
>
>
> 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
