Spring dependencies are analyzed by parsing bean definition files, we do not currently support analysis of Spring dependency injection by annotations. All the beans defined in the xml files are shown as beans in the dependency graph. Spring xml configuration files must be on the class path.

When parsing jars for Spring dependencies, it can occur that the jars remain "locked" after parsing. This is due to a discrepancy in the Spring parser and out of our reach. To work around this, for example, to allow maven clean succeed whilst our application is still in memory, you can bypass Spring dependency analysis by setting this property to false in our project file:

<property name="include-injected-dependency" value="false" />

The following are the two types of Dependency Injection shown.

1. Constructor based Dependency Injection (CI) : Represents the dependency between constructor and it's arguments, each representing a dependency. These dependencies are named as Injected (CI).
2. Setter based Dependency Injection (SI) : Represents the dependency between beans (setter method is called) and argument passed to the setter method. These dependencies are named as Injected (SI).

Note : Currently only Spring Dependency Injection is supported.