Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
Gump2-2.4
-
None
Description
This list is clearly wrong:
http://lsd.student.utwente.nl/gump/scarab/scarab_details.html#Full+Project+Dependencies
The primary reason is that this count of unique dependency objects (an entity which links to projects) not the results of the dependency itself – the dependent project. Dependency objects are owned (they form a bi-directional link) and the owner is part of the _eq_ (equality check) which I think is probably valid (albeit annoying here.)
As such when we attempt to count only unique dependencies and does 'if not depend in depends:' – the _eq_ says no. The problem becomes worsened when on considered jars ids. Are two depends on the same project equal if they reference different ids? I'd say no.
I suspect the best thing to do is to keep this up at the project level, find a way to compare two dependencies only by the project they reference. I wonder if Gumpy needs a way to optimize/merge dependencies, so repeats are reduced. That said, there are multiple areas (not jsut counters/lists) that need to have the right answer, and doing this wrong could dork classpaths.
Honestly, I don't know the right way to fix this, hence this JIRA posting to let the thought sit openly for a while...