[
https://issues.apache.org/jira/browse/CONNECTORS-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13065257#comment-13065257
]
Karl Wright commented on CONNECTORS-223:
----------------------------------------
I just ran into a potential issue. The framework tests are organized as
follows:
- the core test package consists of tests and a TestBase class
- the agents test package consists of tests and a TestBase class that extends
the core TestBase class
- the pull-agent test package consists of tests and a TestBase class that
extends the agents TestBase class
The question is, where should the TestBase classes live? Will maven do the
right thing if these are all moved, to core/src/test/java,
agents/src/test/java, and pull-agent/src/test/java, respectively? Or do we
need specific mcf-core-test, mcf-agents-test, and mcf-pull-agent-test
subprojects, for the test base classes? How is this usually handled in Maven?
> 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
>
> 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
