Merge pull request #478 from yegor256/274

For #274: jPeek maven plugin setup

README.md

@@ -50,6 +50,7 @@ $ java -jar jpeek-jar-with-dependencies.jar --sources . --target ./jpeek
  that jpeek jar accepts and the default values for each parameter.
 -->
 
+
 jPeek will analyze Java files in the current directory.
 XML reports will be generated in the `./jpeek` directory. Enjoy.
 
@@ -267,6 +268,9 @@ Thus, all calculations happen inside the XSLT files. We decided to implement
 it this way after a less successful attempt to do it all in Java. It seems
 that XSL is much more suitable for manipulations with data than Java.
 
+### jPeek maven plugin
+We are developing a jPeek plugin for Maven, see [jPeek Maven plugin](https://github.com/yegor256/jpeek-maven-plugin) project.
+
 ## Known Limitations
 
 * The java compiler is known to inline constant variables as per [JLS 13.1](https://docs.oracle.com/javase/specs/jls/se8/html/jls-13.html#jls-13.1). This affects the results calculated by metrics that take into account access to class attributes if these are `final` constants. For instance, all LCOM* and *COM metrics are affected.