[
https://issues.apache.org/jira/browse/CONNECTORS-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13108900#comment-13108900
]
Karl Wright commented on CONNECTORS-223:
----------------------------------------
bq. I'm not sure, that packages not available at Maven central, or other
repositories, should be used in pom's - in Tika project another approach is
used - all needed jars are promoted to repository first, and only after it are
used...
If you want to create an example patch that shows how you think we should do
it, I'd certainly have a look at it. But I think you might want to open a new
JIRA ticket for this issue first.
> 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, CONNECTORS-223_forkMode.patch,
> CONNECTORS-223_jetty-runner.patch, CONNECTORS-223_tests.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
