[
https://issues.apache.org/jira/browse/CALCITE-861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14960153#comment-14960153
]
Julian Hyde commented on CALCITE-861:
-------------------------------------
The way I see it, Maven artifacts work fine (you can register main, test,
javadoc, test-javadoc etc. artifacts in a repository, and they can depend on
each other) but it's just the reactor that is broken. If the reactor worked OK
we wouldn't even be having this conversation about whether one test artifact
can depend on another. Obviously it should be OK.
Now imagine someone who has just downloaded Calcite who can't find the tests
because they are in another module. I can imagine an IDEs that can efficiently
rebuild and run tests within the same module but require a longer build process
to rebuild a different module than is being tested.
People will be tempted to start introducing dependencies on test libraries
(jmockit, junit) into core, which would be bad.
It's not unreasonable to expect people to look in the doc to find out that the
build command is {{mvn clean && mvn -DskipTests install && mvn test}}. I'd
rather that than 150 files moved to an unintuitive location.
> 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)
