[
https://issues.apache.org/jira/browse/CALCITE-861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14958412#comment-14958412
]
Julian Hyde commented on CALCITE-861:
-------------------------------------
What you are recommending is consistent with what I found:
http://stackoverflow.com/questions/1725476/maven-test-dependency-in-multi-module-project
Still can't quite believe that the reactor can't handle test artifacts. But
anyway.
When moving "common test infrastructure" to a new module, is there clearly a
right place to cut? If cti depends on core and core-test depends on cti, isn't
that a cyclic dependency? Is that a problem for maven?
> Fix or document issue where first time user cannot use mvn compile
> ------------------------------------------------------------------
>
> Key: CALCITE-861
> URL: https://issues.apache.org/jira/browse/CALCITE-861
> Project: Calcite
> Issue Type: Bug
> Reporter: Jacques Nadeau
> Assignee: Josh Elser
> Fix For: next
>
>
> Having come up from last vote:
> While I managed to get it to compile, note that a “mvn compile” will fail
> with:
> Could not find artifact
> org.apache.calcite:calcite-avatica:jar:tests:1.4.0-incubating in central
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
