Improve fiability of DependencyAnalyzer

[jecisc]

In some cases, the DependencyAnalyzer cannot be sure of some dependencies because there are multiple methods of the same name in the image and it fails to infer which is the right one.

But when showing dependencies at the level of the package, it does not mean that it cannot know from which package the dependency is from.

Example:

On this screen, we see that a method is implemented on 5 objects but the 5 are in the same package. Thus we are sure of the dependency in that case. It would be great of the tool could manage this case.

[stale]

To limit bug bankruptcy (see https://www.joelonsoftware.com/2012/07/09/software-inventory/) this issue has been automatically marked as stale because it has not had any activity in 6 months. If no further activity occurs, it might be closed. If this issue remains important to you, please comment to reactivate the issue. Thank you for your contributions.

Joel on Software

Software Inventory

Imagine, for a moment, that you came upon a bread factory for the first time. At first it just looks like a jumble of incomprehensible machinery with a few people buzzing around. As your eyes adjus…

[jecisc]

keep it

[guillep]

This issue looks more like a small project than an actionable issue.
I propose we move it to a wiki with potential projects for people to contribute.
I'm collecting all these.
Could be a great basis for GSOC.