Java类的依赖工具 [英] Class Dependency Tools for Java

查看:276
本文介绍了Java类的依赖工具的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我知道很多相关问题已经在SO上提供,但是我没有能够找到完全令人满意的内容 - 可能是因为我的要求与提出的这些问题略有不同。

I know a lot of related questions have been given on SO, but I've not been able to find anything fully satisfactory - probably because my requirement is slightly different from each of those questions raised.

我有一个巨大的代码库,我想分解成更小的逻辑单元。为此,我需要找到所有纠缠/循环的依赖关系并解决它们。由于现有意大利面的大小,唯一可行的策略似乎是分而治之,所以我需要先将巨大的项目划分成较小的部分,或者剥离独立部件,分开处理较小的部件。

I have a gigantic codebase that I'd like to break down into smaller logic units. To do this, I need to find all the tangled/circular dependencies and resolve them. Due to the size of the existing spaghetti, the only feasible strategy appears to be divide-and-conquer, so I need to divide the huge project into smaller pieces first or peel off independent parts and tackle the smaller pieces separately.

我可以找到的大多数工具似乎只能在类或包级别上工作,但它们似乎不支持子包的概念。例如,如果我有一个根包,3个包,然后在3个的每个5个子包,那么我会得到1 + 3 + 15 = 19包,这将给我一个疯狂复杂的图。现在我希望能够做的是首先分析3个顶级包之间的依赖关系(传入/传出包的数量,以及哪些类来源于这些依赖关系),然后在这个层次上进行清理,再进入这些顶部

Most of the tools I can find out there seems to only work on the class or package level, but they don't seem to support the concept of sub-packages. For example, If I have a root package, 3 packages under that, and then 5 subpackages under each of the 3, then I'll get 1+3+15=19 packages, which will give me a crazily complicated graph. Now what I hope to be able to do is to analyze the dependency relationship between the 3 top level packages first (number of incoming/outgoing packages, and which classes originate these dependencies), clean it up on that level, before diving into these top level packages to work on the next level.

现在,我已经使用了结构101来达到这个目的,而且效果很好,但是当试用期满时,该产品对我的预算有点陡峭。是否有免费/开源解决方案?

Now, I've used Structure 101 for this purpose, and it works great, but when the trial expires, the price of the product is a little steep for my budget. Is there a free/open source solution out there?

提前感谢!

推荐答案

据我所知,没有免费的工具可以与结构101 进行远程比较。 (我不隶属!)

To my knowledge there is no free tool that is remotely comparable to structure 101. (I am not affiliated!)

所以你已经有一个解决方案,但你说定价太高了。这可能是一个谬误。

So you already have a solution, but you say the pricing is too high. This may be a fallacy.


我有一个巨大的代码库,我想分解成更小的逻辑单元。

I have a gigantic codebase that I'd like to break down into smaller logic units.

大概你不是这样做,但有人付钱给你做。结构101的900美元是大约3-4天的工作 - 假设你每月作为香港的高级软件开发商每月赚取40,000港元(5200美元)。应该可以做出这样的论据,这样做实际上可以节省很多钱。

Presumably you're not doing this for fun but somebody is paying you to do it. The USD 900 for structure 101 is around 3-4 days of work - assuming you make something like HKD 40k (USD 5200) per month as a senior software developer in Hong Kong. It should be possible to make the argument that this will actually save a lot of money in the end.

这篇关于Java类的依赖工具的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆