Open vprudnikov opened 6 years ago
That's a limitation deriving from the fact that jQA uses Java bytecode for scanning: the Java compiler inlines constant values into the compiled files so the scanner cannot see that there has been a dependency in the source code.
Thank you for your reply. Can you suggest anything to overcome this issue?
Sadly I have no idea without affecting the source code:
public class Controller {
String CONST = "qwe".intern();
}
In this case you'll see the dependency it's strange for the devs and furthermore you cannot see the constant's value in the graph.
OK, thank you! At least this information would be helpful for others :)
This is a documenation issue, need to identify a place where this fits bests in. It should be mentioned in the Java scanner but maybe its also an worth pointing this out in a 101 tutorial that handles dependencies, e.g. https://101.jqassistant.org/manage-package-dependencies/index.html
Hello,
I'm trying to detect dependencies between classes from different packages.
I have to classes:
When I run a query for collecting all dependencies
MATCH (type1:Type)-[:DEPENDS_ON]->(type2:Type) RETURN type1,type2
...I see that both
Controller
andEntity
depend onjava.lang.String
.Entity
doesn't depend onController
.But it doesn't help me to resolve the introduced dependency between domain and controller layers.
Any workaround?
Thank you.