You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Chetan Mehrotra (JIRA)" <ji...@apache.org> on 2015/05/27 07:21:17 UTC
[jira] [Updated] (OAK-2911) Analyze inter package dependency in
oak-core
[ https://issues.apache.org/jira/browse/OAK-2911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chetan Mehrotra updated OAK-2911:
---------------------------------
Attachment: oak-core-jdepend-report.html
[attached |^oak-core-jdepend-report.html] is jdepend report for oak-core obtained via
{noformat}
mvn jdepend:generate
{noformat}
> Analyze inter package dependency in oak-core
> --------------------------------------------
>
> Key: OAK-2911
> URL: https://issues.apache.org/jira/browse/OAK-2911
> Project: Jackrabbit Oak
> Issue Type: Task
> Components: core
> Reporter: Chetan Mehrotra
> Assignee: Chetan Mehrotra
> Priority: Minor
> Fix For: 1.3.1
>
> Attachments: oak-core-jdepend-report.html
>
>
> For better code health the packages should have proper inter dependency. Its preferable that various {{plugin}} packages within oak-core have minimal inter dependency and should be able to exist independently.
> Following work need to be performed
> # Check whats the current state
> # Look into ways to ensure that such dependency are minimal and at minimum must not have cycle
> See
> * http://stackoverflow.com/questions/3416547/maven-jdepend-fail-build-with-cycles
> * https://github.com/andrena/no-package-cycles-enforcer-rule
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)