Dependency viewer: things I'd like (expect) to see in the final version

Hi there,

Now I know that some of the things below might have already been discussed (and I probably missed them), or they might already be in there and I haven't figured out how to get to them, while others might already be under development. Anyway, here are some features I'd like to see in the final version of the dependency viewer:

- ability to view both incoming and outgoing dependencies for a module/package/class (right now I can see what a package depends on, not the other way around)

- totals for the dependencies shown on the lines in the upper pannels (for easier spotting of the packages with lots of dependencies). The ability to sort based on those numbers would be even nicer.

- the ability to mark a dependency as illegal/legal from the dependency viewer (as opposed to having to go through the rules editor dialog)

- the ability to distinguish between different types of dependencies (class hierarchy vs. composition vs. used from method parameters, for instance) and to assign different severities to those types when marked as illegal.

What do you think, any chance we'll get some of these in Pallada?

Thx,
Andrei


7 comments
Comment actions Permalink

- ability to view both incoming and outgoing dependencies for a module/package/class (right now I can see what a package depends on, not the other way around)


+1000

- the ability to mark a dependency as illegal/legal from the dependency viewer (as opposed to having to go through the rules editor dialog)


+1
Good idea, especially because the rule editor is horrible - at least the
last time I've checked.

- the ability to distinguish between different types of dependencies (class hierarchy vs. composition vs. used from method parameters, for instance) and to assign different severities to those types when marked as illegal.


+1
Also a very good idea.

Tom

0
Comment actions Permalink

Thomas Singer (MoTJ) wrote:
> +1
> Good idea, especially because the rule editor is horrible - at least the
> last time I've checked.

Please recheck :)

--
Maxim Shafirov
IntelliJ Labs / JetBrains Inc.
http://www.intellij.com
"Develop with pleasure!"

0
Comment actions Permalink

>> Good idea, especially because the rule editor is horrible - at least
>> the
>> last time I've checked.
MS> Please recheck :)
MS>

Does this mean we're not going to be able to right click on a dependency and mark it as illegal? ;)

Thx,
Andrei

0
Comment actions Permalink

Andrei Oprea wrote:

>>>Good idea, especially because the rule editor is horrible - at least
>>>the
>>>last time I've checked.


MS> Please recheck :)
MS>

Does this mean we're not going to be able to right click on a dependency and mark it as illegal? ;)

Thx,
Andrei

Not in Pallada I'm affraid. All those ideas are really good but we're to stop feature development for now.

--
Maxim Shafirov
IntelliJ Labs / JetBrains Inc.
http://www.intellij.com
"Develop with pleasure!"

0
Comment actions Permalink

Andrei Oprea wrote:

What do you think, any chance we'll get some of these in Pallada?

Thx,
Andrei

My biggest request would be to make it easy to find dependency cycles.
See http://www.intellij.net/tracker/idea/viewSCR?publicId=33305

--
Rob Harwood
Software Developer
JetBrains Inc.
http://www.jetbrains.com
"Develop with pleasure!"

0
Comment actions Permalink

MS> Not in Pallada I'm affraid. All those ideas are really good but
MS> we're to stop feature development for now.
MS>

Too bad. The dependency analyzer is a really nice addition to IDEA, but I'm afraid it's missing some vital functionality, the fact that it goes only one way for checking dependencies is a serious limitation, IMHO. The other suggestions are really "nice-to-have" things (but, hey!, we're used to getting the best possible implementation in IDEA).

As it is now, one would still have to use another product in order to get a better picture of the dependencies in a project (http://javacentral.compuware.com/products/optimaladvisor does a good job, for instance).

Best regards,
Andrei

0
Comment actions Permalink


> dependency cycles.
+10

and +10 on the other suggestions.

I would also like to see in the tree the ability to sort by rules that were broken or to see besides each offending class, which rules did they break.

Although I must admit that the current state of the Dep An has not allowed me to use it much... as of 2026 rules that depended on module specificity were not saved correctly.

Florian Hehlen

0

Please sign in to leave a comment.