scanning of related jar files creates redundant Interface nodes

[torstenwerner]

Hi,

I'll attach a sample project with 2 jar files. 1 jar contains an interface SampleApi and the 2nd jar contains a class SampleImpl that implements this interface. I'll get 2 separate nodes with name SampleApi after scanning with jqassistant. One node is correctly labeled Interface but it is not connected to the SampleImpl node. The other node is not labeled Interface but is connected to the SampleImpl node.

I would expect to get just a single node SampleApi with label Interface and which is connected to the SampleImpl node.

sample sources and binaries: twojars.zip

Torsten