You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by "László Bodor (Jira)" <ji...@apache.org> on 2020/02/22 18:32:00 UTC
[jira] [Commented] (TEZ-4118) tez-common module should not depend
on tez-api
[ https://issues.apache.org/jira/browse/TEZ-4118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17042671#comment-17042671 ]
László Bodor commented on TEZ-4118:
-----------------------------------
[~jeagles]: I guess it makes no sense to refactor the submodules like this, so I'm about to close this as won't fix
just for confirmation, e.g. the duplicated Preconditions class from TEZ-4101 will be placed only into tez-api with a follow-up ticket ([reference|https://issues.apache.org/jira/browse/TEZ-4101?focusedCommentId=17021623&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17021623])
> tez-common module should not depend on tez-api
> ----------------------------------------------
>
> Key: TEZ-4118
> URL: https://issues.apache.org/jira/browse/TEZ-4118
> Project: Apache Tez
> Issue Type: Improvement
> Reporter: László Bodor
> Assignee: László Bodor
> Priority: Major
>
> While creating TEZ-4101 I found that tez-common depends on tez-api, while "common" name implies that it's a utility module that is not supposed to depend on others. But it seems like, tez-api is the one which doesn't depend on other tez modules (maybe it's intentional?).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)