directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Lecharny (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FC-109) break core package cycles
Date Tue, 02 Jun 2015 04:49:17 GMT

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

Emmanuel Lecharny commented on FC-109:
--------------------------------------

Sounds like the right thing to do.

Can you confirm that those classes are going to be moved in the 'model' package ?
:

Address
Administrator
AdminRole
AdminRoleRelationship
AdminUtil
AuthZ
Bind
FortEntity
Graphable
Hier
Mod
OrgUnit
OrgUnitAnt
OrgUnitRelationship
PermGrant
Permission
PermObj
Props
PwMessage
PwPolicy
PwPolicyControl
Relationship
Role
RolePerm
RoleRelationship
SDSet
Session
User
UserAdminRole
UserAudit
UserRole
Warning

I think there is only two package cycles in this case : 
* the {{UserAdminRole}} class depends on the rbac package {{RoleUtil}} class
* the {{UserRole}} class depends on the rbac package {{RoleUtil}} class

It might be necessary to split the {{RoleUtil}} class into two fragments.

> break core package cycles
> -------------------------
>
>                 Key: FC-109
>                 URL: https://issues.apache.org/jira/browse/FC-109
>             Project: FORTRESS
>          Issue Type: Sub-task
>    Affects Versions: 1.0.0-RC41
>            Reporter: Shawn McKinney
>             Fix For: 1.0.0
>
>
> remove the package cycles from the core by moving the entities into a separate package
named 'model'.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message