JavaInspect - Utility to visualize java software

1. General +
- 1.1. Source code
+
2. Goal and operating principle
3. Example graphs
4. Installation
5. Usage +
- 5.1. Usage as commandline utility +
  - 5.1.1. Available commandline arguments
  - 5.1.2. Specifying classes to render
  +
- 5.2. Usage via Java API +
  +
+
6. TO DO
7. See also

1 General

This program is free software: you can redistribute it and/or modify it under the terms of the GNU Lesser General Public License as published by the Free Software Foundation, either version 3 of the -License, or (at your option) any later version. -
Program authors:
- Svjatoslav Agejenko
  - Homepage: https://svjatoslav.eu -
  - Email: mailto://svjatoslav@svjatoslav.eu -
  - Other software projects hosted at svjatoslav.eu -
  -
- Homepage: https://svjatoslav.eu
- Email: mailto://svjatoslav@svjatoslav.eu
- Other software projects hosted at svjatoslav.eu
Tony Bargnesi
- GitHub fork for the project: -https://github.com/abargnesi/javainspect -
-

- +https://github.com/abargnesi/javainspect + +

1.1 Source code

Download latest snapshot in TAR GZ format -
Download latest snapshot in TAR GZ format
Browse Git repository online -
Browse Git repository online
Clone Git repository using command: +

+Clone Git repository using command: +

 git clone https://www2.svjatoslav.eu/git/javainspect.git
-
-

2 Goal and operating principle

Goal: simplify/speed up understanding the computer program code by @@ -266,15 +321,15 @@ automatically visualizing its structure.

-JavaInspect can be used as a standalone commandline utility as well as -java library. JavaInspect uses primarily Java built-in reflection to +JavaInspect can be used as a standalone commandline utility as well as +java library. JavaInspect uses primarily Java built-in reflection to discover and visualize any part of Java program.

-JavaInspect currently has no GUI, configuration files, embedded -scripting support, direct Maven or Ant integration. See usage to learn -how to instuct Javainspect what to do. +JavaInspect currently has no graphical user interface, configuration +files, embedded scripting support, direct Maven, Gradle or Ant +integration. See usage to learn how to instuct Javainspect what to do.

@@ -288,111 +343,207 @@ bitmap graph in PNG or SVG format. Notes:

JavaInspect is developed and tested so far only on GNU/Linux. -
See: Madge - similar tool for JavaScript -
JavaInspect is developed and tested so far only on GNU/Linux.

3 Example graphs

A very simple example: +
+A very simple example: +
-
-
+
+

-
+

Graph legend:

- +

4 Usage

4 Installation

-JavaInspect can be controlled in 2 different ways: +GraphViz - shall be installed on the computer.

as standalone commandline utility -
as embedded Java library via Java API -

+ +

+On Ubuntu/Debian GraphViz can be installed using: +

sudo apt-get install graphviz
+

4.1 usage as commandline utility

-To enable commandline support, (study and) execute script: +To use JavaInspect via Java API, no further installation is +needed. JavaInspect will be embedded into your project as dependency. +This is described in usage via Java API. It will expect GraphViz to be +available in the system. +

+ +

+To use JavaInspect as a commandline tool, JavaInspect source +repository has to be cloned locally: See Source code. +

+ +

+Then study and execute installation script:

 commandline launcher/install
+

+ +

+After installation, new commandline tool should be available +

+javainspect

-Warning: It was tested only on Debian Stretch linux. +Quick commandline usage help can be viewed by issuing

+javainspect --help
+

5 Usage

-Available commandline arguments: +JavaInspect can be controlled in 2 different ways:

as standalone commandline utility
as embedded Java library via Java API

+ +

5.1 Usage as commandline utility

5.1.1 Available commandline arguments

--j (existing files)…
-    JAR file(s) to render.
-
--n (mandatory, string)
-    Graph name.
-
-–debug
-    Show debug info.
-
--k
-    Keep dot file.
-
--h
-    Hide orphaned classes.
-
--w (one to many strings)…
-    Whitelist glob(s).
-
--b (one to many strings)…
-    Blacklist glob(s).
-
--d (existingdirectory)
-    Target directory. Default is current directory.
-
--t (options: png, svg)
-    Target image type. Default is: svg.
-

4.2 usage via Java API

+-j (existing files)…
+    JAR file(s) to render.
+
+-c (existing directories)…
+    Classpath directories
+
+-n (string)
+    Graph name. (default: "graph")
+
+–debug
+    Show debug info.
+
+-h, –help
+    Show commandline usage help.
+
+-k
+    Keep dot file.
+
+-ho
+    Hide orphaned classes.
+
+-w (one to many strings)…
+    Whitelist glob(s).
+
+-b (one to many strings)…
+    Blacklist glob(s).
+
+-r (one to many strings)…
+    root class(es).
+
+-d (existing directory)
+    Target directory. Default is current directory.
+
+-t (options: png, svg)
+    Target image type. Default is: svg.
+

5.1.2 Specifying classes to render

+Normal Java application has immense complexity. In addition to code +that was directly written by particular project developers, lots of +functionality is typically added as frameworks or libraries to the +project. In addition there is significant Java standard library. +

+ +

+Because JavaInspect uses reflection, it does not easily distinguish +between those. In normal situation you would rather want to visualize +only code that was developed specifically for your project and leave +frameworks like Spring etc. out. If you visualize all classes that are +possibly reachable from you project, you will easily get huge and +incomprehensible graph. +

+ +

+JavaInspect can digest compiled Java classes in 2 modes: +

Provide list of Jar files. Use -j option.
Provide list of filesystem directories that can be used as +classpath root. Use -c option.

+ +

+Currently JavaInspect uses following algorithm to add classes to +rendered graph: +

+ +

All classes that were found in Jar files are added to graph by default.
None of the classes that were found in filesystem directories are +added to the graph by default (unless explicitly referenced). (TODO: +for consistency it would be better to add them too by default)
If whitelist is specified (-w option) everything that is not +matched by whitelist pattern(s) will be removed from the graph.
If blacklist is specified (-b option) everything that is matched +by blacklist pattern(s) will be removed from the graph.
Root classes can be specified using -r option. Root classes will +be added to the graph. JavaInspect will then try to recursively +discover all classes that were referenced by root class and add +those also to the graph.

+ +

5.2 Usage via Java API

Requires that classes to be visualised are available in the classpath.

@@ -403,15 +554,13 @@ up with 2 solutions:

Add JavaInspect library in your project as a dependency. -
Add JavaInspect library in your project as a dependency.
Create new Java project for the purpose visualizing your other projects and include JavaInspect and your projecs binary artifacts (Jar's) into new project classpath. Built binary Jar's (with no source code) are sufficient because JavaInspect operates via -reflection. -

@@ -425,48 +574,40 @@ product or project artifact I'm just willing to visualize. Control code in general does the following:

Create graph object. -
Create graph object.
Java reflection/classloaders does not provide mechanism for discovering all classes under given package. Therefore you need to declare at least some classes to be added to the graph by manually adding individual classes to the graph. For every class added to the graph, GraphViz will recursively inspect it and add all -referecned classes to the graph as well. -
Graphs easilly get very big and complex so optionally we filter important code using classname glob patterns based blacklist and/or -whitelist. -
Optionally we can tune some rendering parameters like:
- Possibility to remove orphaned classes (classes with no -references) from the graph. -
- Specify target directory for generated visualization -files. (Default is current directory) -
- Keep intermediate GraphViz dot file for later inspection. -
-
Render graph. -
Keep intermediate GraphViz dot file for later inspection.
Render graph.

4.2.1 example 1: individually picked objects

5.2.1 Example 1: individually picked objects

This example demonstrates generating of class graph from hand picked classes and visualizing GraphViz itself.

- -

// Create graph
++// Create graph
 final ClassGraph graph = new ClassGraph();
 
 // Add some random object to the graph. GraphViz will detect Class from
@@ -490,7 +631,6 @@ graph.generateGraph("JavaInspect");
 Note: if desired, more compact version of the above:
 
 
-
 new ClassGraph().add(randomObject, RandomClass.class)
                 .setKeepDotFile(true).generateGraph("JavaInspect");
 
@@ -501,34 +641,29 @@ Note: if desired, more compact version of the above:
 Result:
 
 
-Generated DOT file: JavaInspect.dot
-
-Generated PNG image: JavaInspect.png
-
+Generated DOT file: JavaInspect.dot
+Generated PNG image: JavaInspect.png

4.2.2 example 2: GraphViz embedded in another project

5.2.2 Example 2: GraphViz embedded in another project

Download project Sixth code snapshot. -
Inspect and run DataGraph.java. -
Download project Sixth code snapshot.
Inspect and run DataGraph.java.

4.2.3 Embedding JavaInspect in your Maven project

5.2.3 Embedding JavaInspect in your Maven project

Declare JavaInspect as dependency:

<dependencies>
     ...
     <dependency>
@@ -546,7 +681,6 @@ Declare JavaInspect as dependency:
 Add Maven repository to retrieve artifact from:
 
 
-
 <repositories>
     ...
     <repository>
@@ -563,25 +697,8 @@ Add Maven repository to retrieve artifact from:

5 Requirements

-GraphViz - shall be installed on the computer. -

- -

-On Ubuntu/Debian use: -

- -

sudo apt-get install graphviz
-

6 TO DO

Note: Because this is side project (and I have many of them) I can @@ -593,24 +710,19 @@ LOT of cool ideas could be implemented. For intstance:

BUG: Should not hide references if there are too many of them to classes if referring classes are not visible anyway because of blacklist/whitelist rules. Basically reference counting should -exclude not visible classes. -

+exclude not visible classes.

BUG: Orphaned class removal does not work always. There are many -bugs and corner cases to find and fix still. -

+bugs and corner cases to find and fix still.

BUG: Code is not very readable. Document and refactor for better -maintainability. -

+maintainability.

FEATURE: Create installable DEB package.

Submit it to some Debian developer for integration or become -Debian package maintainer. -

+Debian package maintainer. +

FEATURE: Make it modular. That is: central part, an application model could be standalone and serializable. @@ -619,128 +731,81 @@ model could be standalone and serializable.

There could be multiple ways to acquire model:

By introspecting application via Java reflections (current mode -of operation). -
By parsing java source. (unfinished) -

+of operation). +

By parsing java source. (unfinished)

There could be ways to manipulate model:

Store/load/compare. -
Trim uninteresting parts. -
Highlight important parts. -

Store/load/compare.

Trim uninteresting parts.

Highlight important parts.

There could be multiple ways to render model:

PNG/SVG (currently implemented) -
PlantUML (TODO) -
Interactive 3D visualization (TODO) -

- - +

PNG/SVG (currently implemented)

PlantUML (TODO)

Interactive 3D visualization (TODO)

+ +

FEATURE: Implement (or integrate existing java parser https://javaparser.org/) to be able to produce code visualizations based on source code (in addition to current reflection based -approach). -

+approach). -

FEATURE: Integarte with PlantUML. -

FEATURE: Integarte with PlantUML.

FEATURE: Add dark theme for generated graphs. -

FEATURE: Add dark theme for generated graphs.

FEATURE: Sort Class fields by alphabet. -

FEATURE: Sort Class fields by alphabet.

FEATURE: Visualize also concrete field values so it could be used as -ultra cool runtime logging/debugging framework. -

+ultra cool runtime logging/debugging framework.

FEATURE: Possibility to visualize structure and data from JVM -snapshot. -

+snapshot.

FEATURE: Possibility to attach to remote process to visualize -data/structure using JVM debug port and mechanism. -

+data/structure using JVM debug port and mechanism. -

FEATURE: Possibility to attach to JVM using JVM agent. -

FEATURE: Possibility to attach to JVM using JVM agent.

FEATURE: Possibility to inspect graphs in 3D using Sixth 3D engine. -

FEATURE: Possibility to inspect graphs in 3D using Sixth 3D engine.

FEATURE: Possibility to select classes/fields/values to be visualized in some graph query language. For greater flexibility in -comparison to currently supported glob syntax. -

+comparison to currently supported glob syntax.

FEATURE: Add option to control JavaInspect via JSON or XML config file. For example different graphs for given project could be defined once in plain text config, possibly with the aid of some interactive utility. Then defined graphs could be updated as part of -project build or release process. -

+project build or release process.

FEATURE: Configurable maven plugin to generate graphs as part of the -project build/release process. -

+project build/release process.

7 See also

Similar or alternative solutions:

- diff --git a/doc/index.org b/doc/index.org index b831a37..7c62a16 100644 --- a/doc/index.org +++ b/doc/index.org @@ -27,6 +27,9 @@ https://github.com/abargnesi/javainspect ** Source code +:PROPERTIES: +:ID: 032b7997-f582-4203-b31a-43ef7b654ed6 +:END: - [[https://www2.svjatoslav.eu/gitweb/?p=javainspect.git;a=snapshot;h=HEAD;sf=tgz][Download latest snapshot in TAR GZ format]] - [[https://www2.svjatoslav.eu/gitweb/?p=javainspect.git;a=summary][Browse Git repository online]] @@ -44,9 +47,9 @@ JavaInspect can be used as a [[id:acf1896a-74b4-4914-acf6-a77075e07f25][standalo [[id:bbeeffc8-3767-440d-8d93-ec9124dd60ee][java library]]. JavaInspect uses primarily Java built-in reflection to discover and visualize any part of Java program. -JavaInspect currently has no GUI, configuration files, embedded -scripting support, direct Maven or Ant integration. See [[id:2ad2889e-6c95-4662-b3f4-2c341fc74522][usage]] to learn -how to instuct Javainspect what to do. +JavaInspect currently has no graphical user interface, configuration +files, embedded scripting support, direct Maven, Gradle or Ant +integration. See [[id:2ad2889e-6c95-4662-b3f4-2c341fc74522][usage]] to learn how to instuct Javainspect what to do. After discovering application structure and optionally filtering out unimportant parts, JavaInspect produces GraphViz dot file that @@ -55,12 +58,11 @@ bitmap graph in PNG or SVG format. Notes: + JavaInspect is developed and tested so far only on GNU/Linux. -+ See: [[https://github.com/pahen/madge][Madge - similar tool for JavaScript]] * Example graphs + A very simple example: - file:example.png + [[file:example.png][file:example-thumbnail.png]] Graph legend: @@ -69,6 +71,31 @@ Notes: + [[https://www3.svjatoslav.eu/projects/sixth-3d/graphs/][See example produced graphs]] for [[https://www3.svjatoslav.eu/projects/sixth-3d/][Sixth 3D - 3D engine project]]. +* Installation +[[http://www.graphviz.org/][GraphViz]] - shall be installed on the computer. + +On Ubuntu/Debian GraphViz can be installed using: +#+BEGIN_SRC sh +sudo apt-get install graphviz +#+END_SRC + +To use JavaInspect via Java API, no further installation is +needed. JavaInspect will be embedded into your project as dependency. +This is described in [[id:bbeeffc8-3767-440d-8d93-ec9124dd60ee][usage via Java API]]. It will expect GraphViz to be +available in the system. + +To use JavaInspect as a commandline tool, JavaInspect source +repository has to be cloned locally: See [[id:032b7997-f582-4203-b31a-43ef7b654ed6][Source code]]. + +Then study and execute installation script: +: commandline launcher/install + +After installation, new commandline tool should be available +: javainspect + +Quick commandline usage help can be viewed by issuing +: javainspect --help + * Usage :PROPERTIES: :ID: 2ad2889e-6c95-4662-b3f4-2c341fc74522 @@ -77,30 +104,31 @@ JavaInspect can be controlled in 2 different ways: + [[id:acf1896a-74b4-4914-acf6-a77075e07f25][as standalone commandline utility]] + [[id:bbeeffc8-3767-440d-8d93-ec9124dd60ee][as embedded Java library via Java API]] -** usage as commandline utility +** Usage as commandline utility :PROPERTIES: :ID: acf1896a-74b4-4914-acf6-a77075e07f25 :END: -To enable commandline support, (study and) execute script: -: commandline launcher/install - -Warning: It was tested only on Debian Stretch linux. - -Available commandline arguments: +*** Available commandline arguments #+BEGIN_VERSE -j (existing files)... JAR file(s) to render. --n (mandatory, string) - Graph name. +-c (existing directories)... + Classpath directories + +-n (string) + Graph name. (default: "graph") --debug Show debug info. +-h, --help + Show commandline usage help. + -k Keep dot file. --h +-ho Hide orphaned classes. -w (one to many strings)... @@ -109,13 +137,50 @@ Available commandline arguments: -b (one to many strings)... Blacklist glob(s). --d (existingdirectory) +-r (one to many strings)... + root class(es). + +-d (existing directory) Target directory. Default is current directory. -t (options: png, svg) Target image type. Default is: svg. #+END_VERSE -** usage via Java API +*** Specifying classes to render +Normal Java application has immense complexity. In addition to code +that was directly written by particular project developers, lots of +functionality is typically added as frameworks or libraries to the +project. In addition there is significant Java standard library. + +Because JavaInspect uses reflection, it does not easily distinguish +between those. In normal situation you would rather want to visualize +only code that was developed specifically for your project and leave +frameworks like Spring etc. out. If you visualize all classes that are +possibly reachable from you project, you will easily get huge and +incomprehensible graph. + +JavaInspect can digest compiled Java classes in 2 modes: +1. Provide list of Jar files. Use *-j* option. +2. Provide list of filesystem directories that can be used as + classpath root. Use *-c* option. + +Currently JavaInspect uses following algorithm to add classes to +rendered graph: + +- All classes that were found in Jar files are added to graph by default. +- None of the classes that were found in filesystem directories are + added to the graph by default (unless explicitly referenced). (TODO: + for consistency it would be better to add them too by default) +- If whitelist is specified (*-w* option) everything that is not + matched by whitelist pattern(s) will be removed from the graph. +- If blacklist is specified (*-b* option) everything that is matched + by blacklist pattern(s) will be removed from the graph. +- Root classes can be specified using *-r* option. Root classes will + be added to the graph. JavaInspect will then try to recursively + discover all classes that were referenced by root class and add + those also to the graph. + +** Usage via Java API :PROPERTIES: :ID: bbeeffc8-3767-440d-8d93-ec9124dd60ee :END: @@ -157,7 +222,7 @@ Control code in general does the following: 5. Render graph. -*** example 1: individually picked objects +*** Example 1: individually picked objects This example demonstrates generating of class graph from hand picked classes and visualizing GraphViz itself. @@ -193,7 +258,7 @@ Result: - Generated DOT file: [[file:JavaInspect.dot][JavaInspect.dot]] - Generated PNG image: [[file:JavaInspect.png][JavaInspect.png]] -*** example 2: GraphViz embedded in another project +*** Example 2: GraphViz embedded in another project 1. Download project Sixth [[https://www2.svjatoslav.eu/gitweb/?p=sixth.git;a=snapshot;h=HEAD;sf=tgz][code snapshot]]. 2. Inspect and run *DataGraph.java*. @@ -226,13 +291,6 @@ Add Maven repository to retrieve artifact from: #+END_SRC -* Requirements -[[http://www.graphviz.org/][GraphViz]] - shall be installed on the computer. - -On Ubuntu/Debian use: -#+BEGIN_SRC sh -sudo apt-get install graphviz -#+END_SRC * TO DO Note: Because this is side project (and I have many of them) I can only contribute few hours per year at average. Any help is welcome. A @@ -310,3 +368,4 @@ LOT of cool ideas could be implemented. For intstance: * See also Similar or alternative solutions: + http://www.class-visualizer.net/ ++ [[https://github.com/pahen/madge][Madge - similar tool for JavaScript]] diff --git a/src/main/java/eu/svjatoslav/inspector/java/commandline/CommandlineConfiguration.java b/src/main/java/eu/svjatoslav/inspector/java/commandline/CommandlineConfiguration.java index 2f8feca..a573a57 100644 --- a/src/main/java/eu/svjatoslav/inspector/java/commandline/CommandlineConfiguration.java +++ b/src/main/java/eu/svjatoslav/inspector/java/commandline/CommandlineConfiguration.java @@ -11,19 +11,20 @@ public class CommandlineConfiguration { public StringParameters whitelistGlob; public StringParameters blacklistGlob; public StringParameters rootClasses; + public NullParameter showHelp; public TargetImageTypeParameter targetImageType; public NullParameter keepDotFile; public DirectoryParameter targetDirectory; + public DirectoryParameters classPaths; public final boolean configurationOk; public NullParameter hideOrphanedClasses; + Parser parser; public static final String DEFAULT_GRAPH_NAME = "graph"; public CommandlineConfiguration(String[] args) { - Parser parser = buildCommandlineParameterParser(); + parser = buildCommandlineParameterParser(); configurationOk = parser.parse(args); - if (!configurationOk) - parser.showHelp(); } public boolean isDebug() { @@ -38,6 +39,11 @@ public class CommandlineConfiguration { .mustExist() .addAliases("-j"); + classPaths = parser.add( + new DirectoryParameters("Classpath directories")) + .mustExist() + .addAliases("-c"); + graphName = parser.add( new StringParameter("Graph name. (default: \"" + DEFAULT_GRAPH_NAME + "\")", DEFAULT_GRAPH_NAME)) .addAliases("-n"); @@ -46,13 +52,16 @@ public class CommandlineConfiguration { new NullParameter("Show debug info.")) .addAliases("--debug"); + showHelp = parser.add(new NullParameter("Show commandline usage help.")) + .addAliases("-h", "--help"); + keepDotFile = parser.add( new NullParameter("Keep dot file.")) .addAliases("-k"); hideOrphanedClasses = parser.add( new NullParameter("Hide orphaned classes.")) - .addAliases("-h"); + .addAliases("-ho"); whitelistGlob = parser.add( new StringParameters("Whitelist glob(s).")) diff --git a/src/main/java/eu/svjatoslav/inspector/java/commandline/Main.java b/src/main/java/eu/svjatoslav/inspector/java/commandline/Main.java index d4d144a..0c63a55 100644 --- a/src/main/java/eu/svjatoslav/inspector/java/commandline/Main.java +++ b/src/main/java/eu/svjatoslav/inspector/java/commandline/Main.java @@ -19,9 +19,13 @@ import java.util.jar.JarInputStream; public class Main { public static void main(String[] args) throws IOException, ClassNotFoundException { CommandlineConfiguration configuration = new CommandlineConfiguration(args); - if (!configuration.configurationOk) + if (!configuration.configurationOk) { + configuration.parser.showHelp(); System.exit(1); - + } + + if (configuration.showHelp.isSpecified()) configuration.parser.showHelp(); + getClassGraph(configuration).generateGraph(configuration.graphName.getValue()); if (configuration.isDebug()) @@ -32,7 +36,7 @@ public class Main { List jarFiles = configuration.jarFiles.getValue(); URLClassLoader classLoader = new URLClassLoader( - getFileUrls(jarFiles), + getClasspathUrls(jarFiles, configuration.classPaths.getValue()), configuration.getClass().getClassLoader()); ClassGraph classGraph = new ClassGraph(); @@ -45,7 +49,7 @@ public class Main { classGraph.setKeepDotFile(configuration.keepDotFile.getValue()); - if (configuration.rootClasses.isSpecified()){ + if (configuration.rootClasses.isSpecified()) { // add only selected root classes for (String rootClass : configuration.rootClasses.getValue()) attemptClassAdditionByName(classLoader, classGraph, configuration, rootClass); @@ -64,8 +68,17 @@ public class Main { return classGraph; } - private static URL[] getFileUrls(List jarFiles) { + private static URL[] getClasspathUrls(List jarFiles, List classpathDirectories) { List urls = new ArrayList<>(); + + classpathDirectories.forEach(classpathDirectory -> { + try { + urls.add(classpathDirectory.toURI().toURL()); + } catch (MalformedURLException e) { + throw new RuntimeException(e); + } + }); + jarFiles.forEach((File file) -> { try { urls.add(file.toURI().toURL()); @@ -90,7 +103,7 @@ public class Main { System.out.println("Adding class to graph: " + className); try { classGraph.add(loadClassByName(classLoader, className)); - } catch (NoClassDefFoundError e){ + } catch (NoClassDefFoundError e) { if (configuration.isDebug()) System.out.println("Class definition was not found."); // Sometimes referenced classes are not found in the same Jar. -- 2.20.1

JavaInspect - Utility to visualize java software

JavaInspect - Utility to visualize java software

Table of Contents

1 General

1 General

1.1 Source code

1.1 Source code

2 Goal and operating principle

2 Goal and operating principle

3 Example graphs

3 Example graphs

4 Usage

4 Installation

4.1 usage as commandline utility

5 Usage

5.1 Usage as commandline utility

5.1.1 Available commandline arguments

4.2 usage via Java API

5.1.2 Specifying classes to render

5.2 Usage via Java API

4.2.1 example 1: individually picked objects

5.2.1 Example 1: individually picked objects

4.2.2 example 2: GraphViz embedded in another project

5.2.2 Example 2: GraphViz embedded in another project

4.2.3 Embedding JavaInspect in your Maven project

5.2.3 Embedding JavaInspect in your Maven project

5 Requirements

6 TO DO

6 TO DO

7 See also

7 See also