UmlGraph 与 APIViz 用于 Maven javadoc 生成
I'm wondering if there are any clear reasons to choose UmlGraph over APIViz for javadoc UML diagram generation in a Maven2 build. Are there any integration or features that one has over the other, they seem pretty similar?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
这里有一个关于 UMLGraph 与 apiviz 的有趣主题(提到了 在这个问题上也是如此),我的理解如下:
因此,如果您的项目是公开的,那么 apiviz 无需 Graphviz 即可正常工作,这一点很好。如果你有很多类,那么必须在 javadoc 中到处添加标签是一个很大的痛苦。如果您正在寻找特殊功能,UMLGraph 可能会提供更多。实际上,我认为您应该尝试两者,因为您显然对最终选择的需求和限制有更好的了解。
There is an interesting thread here about UMLGraph vs apiviz (which are mentioned in this question on SO too) and my understanding is the following:
So, if you project is public, the fact that apiviz gracefully works without Graphviz is nice. If you have lots of classes, having to add tags in javadoc everywhere is a big pain. If you're looking for special features, UMLGraph might offer more. Actually, I think you should experiment both as you obviously have a better knowledge of your needs and constraints for the final choice.
apiviz 需要注释来生成图形,这是不正确的,因为它的文档明确指出:
It is not true that apiviz requires annotations for the generation of graphs, as its documentation clearly states: