blocks|key|754881|text|我最近发现了CodePro+AnalytiX，以前是实例化的，现在可以从谷歌免费获得：https://developers.google.com/java-dev-tools/codepro/doc/features/dependencies/dependencies|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|754882|entityMap|0|LINK|mutability|MUTABLE|url|https://developers.google.com/java-dev-tools/codepro/doc/features/dependencies/dependencies^0|17|2J|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

I have recently discovered CodePro AnalytiX, formerly from Instantiations, now available for free from Google: 
<a href="https://developers.google.com/java-dev-tools/codepro/doc/features/dependencies/dependencies" rel="nofollow">https://developers.google.com/java-dev-tools/codepro/doc/features/dependencies/dependencies</a>

blocks|key|754878|text|我使用stan4j实现了同样的目的，但不幸的是，社区版有500个类的限制。另一方面，它也是eclipse的一个扩展。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|754879|entityMap|0|LINK|mutability|MUTABLE|url|http://stan4j.com/dependencies/dependency-analysis.html^0|3|6|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

I used <a href="http://stan4j.com/dependencies/dependency-analysis.html" rel="nofollow">stan4j</a> for the same purpose but unfortunately the community edition has a 500 classes limit. On the other side, it works as an eclipse extension.

blocks|key|323286|text|SonarJ是一个很好的工具，但是它很昂贵。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|323287|另一个非常好的工具是XDepend，它更便宜。为了您的目的，我建议您使用此工具。就质量/价格而言，我认为是最好的选择。|323288|使用更少的功能，您可以使用Sonar+(自由和OpenSource)分析及其依赖矩阵。|323289|entityMap|0|LINK|mutability|MUTABLE|url|http://www.hello2morrow.com/products/sonarj|1|http://www.xdepend.com/|2|http://www.sonarsource.com/^0|0|6|0|0|A|7|1|0|D|5|2|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@$A|U|B|V|1|W]]|C|$]]|$1|D|3|E|5|6|7|X|8|@]|9|@$A|Y|B|Z|1|10]]|C|$]]|$1|F|3|G|5|6|7|11|8|@]|9|@$A|12|B|13|1|14]]|C|$]]|$1|H|3|-4|5|6|7|15|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]|P|$5|K|L|M|C|$N|Q]]|R|$5|K|L|M|C|$N|S]]]]

<a href="http://www.hello2morrow.com/products/sonarj" rel="nofollow">SonarJ</a> is a good tool to do that, but it is expensive.

Another very good tool is <a href="http://www.xdepend.com/" rel="nofollow">XDepend</a>, which is cheaper. For your purpose, I would recommand you this tool. The best choice in terms of quality/price I think.

With much less functionalities, you can use a <a href="http://www.sonarsource.com/" rel="nofollow">Sonar</a> (Free and OpenSource) analysis and its dependencies matrix.

blocks|key|4104061|text|JDepend是一个分析包依赖关系的免费工具。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|4104062|它标识了循环依赖关系，这将阻碍将这个整体划分为更小的部分。|4104063|我们在单元测试中加入了对循环依赖的检查，从一开始就防止了循环依赖。|4104064|有一个对应的Eclipse+plug-in。|4104065|您可以将输出发送到GraphViz。然而，随着软件包数量的增加，可视化变得不那么容易理解。|4104066|现在，Fabian+Steeg首先提到的CodePro+AnalytiX是免费的，值得再看看。至少在被Google购买之前，实例化可以可靠地生产出优秀的软件。几年前，我用过它，除了成本，没有其他抱怨。|4104067|entityMap|0|LINK|mutability|MUTABLE|url|http://www.clarkware.com/software/JDepend.html|1|http://andrei.gmxhome.de/jdepend4eclipse/^0|0|7|0|0|0|0|6|F|1|0|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@$A|Y|B|Z|1|10]]|C|$]]|$1|D|3|E|5|6|7|11|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|12|8|@]|9|@]|C|$]]|$1|H|3|I|5|6|7|13|8|@]|9|@$A|14|B|15|1|16]]|C|$]]|$1|J|3|K|5|6|7|17|8|@]|9|@]|C|$]]|$1|L|3|M|5|6|7|18|8|@]|9|@]|C|$]]|$1|N|3|-4|5|6|7|19|8|@]|9|@]|C|$]]]|O|$P|$5|Q|R|S|C|$T|U]]|V|$5|Q|R|S|C|$T|W]]]]

<a href="http://www.clarkware.com/software/JDepend.html" rel="nofollow">JDepend</a> is a free tool for analyzing package dependencies. 

It identifies circular dependencies, which would impede breaking this monolith into smaller pieces. 

We put this check for circular dependencies into our unit tests, to prevent them from the start.

There's a corresponding <a href="http://andrei.gmxhome.de/jdepend4eclipse/" rel="nofollow">Eclipse plug-in</a>. 

You can send the output to GraphViz. However, the visualization becomes less understandable as the number of packages grows.

Now that CodePro AnalytiX [mentioned first by Fabian Steeg above] is free, it's worth another look. At least prior to purchase by Google, Instantiations reliably produced great software. I played with it some years back, and recall no complaints other than cost.

blocks|key|2674876|text|一个不错的尝试是将您的jar文件反向转换为类图。我找到了这个教程，它解释了如何将由jar文件组成的项目转换为UML类图：http://www.ejb3.org/jar_file_reverse/jar_file_reverse.html。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2674877|您将能够在包级别上查看包关系，还可以查看一个包中与其他包有关系的类。一旦项目被逆转，您可以将其重新组织为模型，并将此文档提供给实现团队。|2674878|​|2674879|📷|atomic|2674880|2674881|entityMap|0|LINK|mutability|MUTABLE|url|http://www.ejb3.org/jar_file_reverse/jar_file_reverse.html|1|IMAGE|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/6e9ca63a8c1b7a675615053b95a85d53.png|imageAlt^0|1O|1M|0|0|0|0|0|1|1|0|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@$A|10|B|11|1|12]]|C|$]]|$1|D|3|E|5|6|7|13|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|14|8|@]|9|@]|C|$]]|$1|H|3|I|5|J|7|15|8|@]|9|@$A|16|B|17|1|18]]|C|$]]|$1|K|3|G|5|6|7|19|8|@]|9|@]|C|$]]|$1|L|3|-4|5|6|7|1A|8|@]|9|@]|C|$]]]|M|$N|$5|O|P|Q|C|$R|S]]|T|$5|U|P|V|C|$W|X|Y|-4]]]]

A good try would be to reverse your jar file into a class diagram. I have found this tutorial which explain how to reverse project composed by jar files into UML class diagram: <a href="http://www.ejb3.org/jar_file_reverse/jar_file_reverse.html" rel="nofollow noreferrer">http://www.ejb3.org/jar_file_reverse/jar_file_reverse.html</a>

You will be able to reverse at package level at see package relation but also to see clases from one package having relation to other packages. Once the project has been reversed you can reorganize it as a model and give this documentation to the implementation team.

<img src="https://www.ejb3.org/jar_file_reverse/display_package_diagram_dependencies.png" alt="alt text">

blocks|key|323295|text|这些类是以正常的方式使用包，还是所有类都在同一个包中？如果第一种情况是真的，我会考虑写一个特殊用途的工具来做第一次剪切。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|323296|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Do the classes use packages in a normal fashion or are all the classes in the same package? If the first case is true, I'd consider writing a special-purpose tool to do the first cut.

blocks|key|4104167|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4104168|它允许您定义切片，即属于一起的类的集合，并将它们可视化为一个可折叠的节点。您的jar将成为切片，您可以对其进行调整，直到它们不再具有任何循环依赖关系，此时它们可以成为自己的jar。|4104169|由于您可以打开切片节点并查看所有包含的类，因此也可以轻松识别可能的重构(引入接口、移动类..)来实现你的目标。|4104170|entityMap^0|0|0|0^^$0|@$1|2|3|-4|4|5|6|G|7|@]|8|@]|9|$]]|$1|A|3|B|4|5|6|H|7|@]|8|@]|9|$]]|$1|C|3|D|4|5|6|I|7|@]|8|@]|9|$]]|$1|E|3|-4|4|5|6|J|7|@]|8|@]|9|$]]]|F|$]]

This is exactly the kind of use case I build <a href="https://github.com/schauder/degraph" rel="nofollow">degraph</a> for.

It allows you to define slices, i.e. sets of classes that belong together, and visualizes them as one collapsible node. You jars to be would be slices that you can tweak until they don't have any more cyclic dependencies, at which point they can become their own jar.

This makes it easy to spot dependencies between slices that you need to break. Since you can open the slice node and see all the contained classes it makes it also easy to identify possible refactorings (introducing interfaces, moving classes ..) to achieve you goal.

We have a Java code base that has grown to be too big for a single monolithic JAR (more than 5000 classes). One of the tasks that we are investigating is how much effort would it be to break this single JAR into smaller components with controlled dependencies between them. However, it's somewhat hard to look at a big bag of code and be sure that you are finding the best points of separation without some analysis.

Are there good tools to inspect and visualize the interpackage dependencies? Given those, we would have a set of suggested cut points where we could begin separating code.

As an example, in the days before Netbeans and Eclipse (and at a different job), we used TogetherJ and TogetherEnterprise. Those had the ability to do a static package analysis and draw the UML diagram. That sort of behavior would be optimal but that feature alone is not sufficient to justify the cost.

Is there a visualization tool that can inspect a Java code base and report inter-package dependencies?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我们有一个Java代码库，对于一个单独的JAR (超过5000个类)来说，它已经变得太大了。我们正在调查的任务之一是，将这个单独的JAR拆分成具有受控依赖关系的较小组件会有多大的工作量。有没有好的工具来检查和可视化包间的依赖关系？考虑到这些，我们将有一组建议的切入点，在这些切入点我们可以开始分离代码。例如，在Netbeans和Eclipse出现之前的日子里(在不同的工作岗位上)，我们使用Toget

问有没有可视化工具可以检查Java代码库并报告包之间的依赖关系？
EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问有没有可视化工具可以检查Java代码库并报告包之间的依赖关系？EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问有没有可视化工具可以检查Java代码库并报告包之间的依赖关系？
EN