[
https://issues.apache.org/jira/browse/CALCITE-861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14960159#comment-14960159
]
Josh Elser commented on CALCITE-861:
------------------------------------
bq. 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.
I'd love to find an answer about this. Perhaps I need to shoot a note over to
their user's list.
bq. can't find the tests because they are in another module
IMO, this isn't that confusing given my breadth of projects. It's pretty common
to see lots of tests all over the place with varying degree. While wholesale
moving all of the tests from core/ elsewhere is a big impact, there are likely
some restricted-in-scope tests which still should live in core/. I just didn't
have the patience to try to move them back yet.
Personally, I find test classes depending on other test classes from another
module to be confusing, but perhaps that's because I know it's a smell with
Maven.
bq. doc to find out that the build command is
The docs already state the following to build the source distribution. Given
your obvious desire to not make these changes, I don't think there's anything
that needs to happen here.
> 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)
