You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@commons.apache.org by "Philip May (JIRA)" <ji...@apache.org> on 2008/02/19 16:18:44 UTC

[jira] Updated: (MODELER-24) Dependency cycle on package level

     [ https://issues.apache.org/jira/browse/MODELER-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Philip May updated MODELER-24:
------------------------------

    Description: 
There is a dependency cycle on package level between org.apache.commons.modeler and org.apache.commons.modeler.modules.
The problem is solved when you move the class ModelerSource into the org.apache.commons.modeler (or a new) package.
This should be done because dependency cycles on package level should be avoided.

  was:
There is an dependency cycle on package level between org.apache.commons.modeler and org.apache.commons.modeler.modules.
The problem is solved when you move the class ModelerSource into the org.apache.commons.modeler (or a new) package.
This should be done because dependency cycles on package level should be avoided.


> Dependency cycle on package level
> ---------------------------------
>
>                 Key: MODELER-24
>                 URL: https://issues.apache.org/jira/browse/MODELER-24
>             Project: Commons Modeler
>          Issue Type: Bug
>    Affects Versions: 2.0.1
>            Reporter: Philip May
>
> There is a dependency cycle on package level between org.apache.commons.modeler and org.apache.commons.modeler.modules.
> The problem is solved when you move the class ModelerSource into the org.apache.commons.modeler (or a new) package.
> This should be done because dependency cycles on package level should be avoided.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.