New in version 2.0
- Don't open Neo4j locally anymore because there were lots compatibility issues. Now REST requests were sent to a running Neo4j.
- Removed Neo4j jars.
- Because of the REST requests, the jQAssistant server can now run on any reachable computer, e.g. a CI server.
New in version 1.1
What is it? Execute queries against an existing jQAssistant database and show results in the Find Toolwindow. So you can search for code using Neo4J Cypher database queries. Usage This plugin doesn't create the jQAssistant database. So you should get a copy from
, configure and run it following the jQAssistant documentation. You can also use the jQAssistant plugins provided by Kontext E available at
. When you have created your database and started the jQAssistant server, you can open the jQA toolwindow. The database location has the default URL where most probably the database files should be found. Take the example query or enter your own and hit the 'Find' button gently. The result is shown in the standard Find toolwindow and you can use it to navigate as you know it. What can you find? You can find classes, methods and files where
- * nodes have a 'fqn' property that contains the fully qualified name of a class in project scope, e.g. nodes with Class, CheckstyleFile, BugInstanceClass (of FindBugs plugin), JacocoClass lables
- * nodes have a 'relativePath' property that contains the path of a file relative to the project root, e.g. with GitFile, GitCommitFile labels
Recent change notes
* Don't open Neo4j locally anymore because there were lots compatibility issues. Now REST requests were sent to a running Neo4j. * Removed Neo4j jars. * Because of the REST requests, the jQAssistant server can now run on any reachable computer, e.g. a CI server.