[ 
https://issues.apache.org/jira/browse/CASSANDRA-14422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16494904#comment-16494904
 ] 

Stefan Podkowinski commented on CASSANDRA-14422:
------------------------------------------------

The dependencies are listed in the parent pom, but not as direct dependencies 
in cassandra-all. As a result, both artifacts won't become a transitive 
dependencies by projects depending on cassandra-all and must get explicitly 
pulled in by such projects. See {{deps-tree-311-no_patch.txt}} on how the 
current dependency tree for 3.11 cassandra-all pom looks like (you won't find 
them there).

Now the question is, will any downstream projects actually need these 
dependencies. But we should probably just be consistent by adding all known 
runtime dependencies to cassandra-all, whether used by nodetool or any other 
place.

> Missing dependencies airline and ohc-core-j8 for pom-all
> --------------------------------------------------------
>
>                 Key: CASSANDRA-14422
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-14422
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Build
>            Reporter: Shichao An
>            Assignee: Shichao An
>            Priority: Minor
>         Attachments: deps-tree-311-no_patch.txt
>
>
> I found two missing dependencies for pom-all (cassandra-all):
>  * airline
>  * ohc-core-j8
>  
> This doesn't affect current build scheme because their jars are hardcoded in 
> the lib directory. However, if we depend on cassandra-all in our downstream 
> projects to resolve and fetch dependencies (instead of using the official 
> tarball), Cassandra will have problems, e.g. airline is required by nodetool, 
> and it will fail our dtests.
> I will attach the patch shortly



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to