oodt-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris A. Mattmann (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OODT-833) Cyclic Dependency
Date Sat, 15 Jul 2017 04:10:00 GMT

    [ https://issues.apache.org/jira/browse/OODT-833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16088433#comment-16088433

Chris A. Mattmann commented on OODT-833:

[~starchmd@umich.edu] this would be a valuable fix - got time to implement it?

> Cyclic Dependency
> -----------------
>                 Key: OODT-833
>                 URL: https://issues.apache.org/jira/browse/OODT-833
>             Project: OODT
>          Issue Type: Bug
>          Components: radix
>            Reporter: Michael Starch
>            Assignee: Michael Starch
>             Fix For: 1.1
>         Attachments: evil-cycle.png, fixed.png
> Currently in the radix poms, there are a cyclic dependencies. This causes ALL dependent
libraries for all of radix to be pulled into each component.  This is incorrect behavior for
components that are supposed to be independent.
> Currently the cyclic dependency shows itself in the following way:
>  FileManager --> Extensions -->PCS Core --> FileManager, Workflow, Resource
> As can be seen, there is a cyclic dependency.
> It is recommended that the top level projects in radix for FileManager, WorkflowManager,
ResourceManager, etc should be broken down into two projects: deployment and core.
> In this way, extensions can depend on core projects, and deployment can depend on both
extensions, and core.  Therefore, the cycle has disappeared.
> At this point, in-order to prevent pulling in dependencies from the non-component cores,
define the dependencies inside Extensions to "provided".

This message was sent by Atlassian JIRA

View raw message