[
https://issues.apache.org/jira/browse/OOZIE-2966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16991422#comment-16991422
]
Mate Juhasz commented on OOZIE-2966:
------------------------------------
The idea is good and valid I think, but the solution is not that trivial
unfortunately. If we move the test classes to the client project we would need
to reference for example to core and fluent-job sub-projects and that would
mean circular dependencies among core and client.
The only solution for resolving the circularity is to restructure a lot of
code, but this way I dont think it worth the time.
> OozieCLI and TestOozieCLI test class are in different packages
> --------------------------------------------------------------
>
> Key: OOZIE-2966
> URL: https://issues.apache.org/jira/browse/OOZIE-2966
> Project: Oozie
> Issue Type: Task
> Components: tests
> Affects Versions: 4.3.0
> Reporter: Artem Ervits
> Assignee: Artem Ervits
> Priority: Trivial
>
> OozieCLI class is in client/org/apache/oozie/cli whereas the associated test
> class resides in core/org/apache/oozie/client shouldn't they belong to same
> project?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
