docs: update usage (#98)

Author: algomaster99

README.md

@@ -55,38 +55,57 @@ mvn clean install -DskipTests
 
 ### How to use
 
-In order to achieve runtime dependencies introspection with classport, you have to first embedd and then to run the instrospector together with you application.
+In order to achieve runtime dependencies introspection with classport, you have to first embed and then to run the instrospector together with you application.
 
 1. Embed
 Inside the target project folder.
+
+Add the following profile to the `pom.xml` file of the project you want to embed.
+To try out introspection, you should add this to the `pom.xml` file of the project which generates the executable jar (with `Main-Class` in the manifest).
+```xml
+<profile>
+  <id>embed</id>
+  <build>
+    <plugins>
+      <plugin>
+        <groupId>io.github.project</groupId>
+        <artifactId>classport-maven-plugin</artifactId>
+        <version>0.1.0-SNAPSHOT</version>
+        <executions>
+          <execution>
+            <id>classport-embed</id>
+            <goals>
+              <goal>embed</goal>
+            </goals>
+          </execution>
+        </executions>
+      </plugin>
+    </plugins>
+  </build>
+</profile>
+```
+Then run the following command to embed the dependencies into the project.
 ```bash
-mvn compile io.github.project:classport-maven-plugin:0.1.0-SNAPSHOT:embed
-mvn package -Dmaven.repo.local=classport-files -DskipTests -Dmaven.main.skip
+mvn clean package -DskipTests -Pembed
 ```
-> Note: `-Dmaven.main.skip` is used to skip the main class compilation and packaging.
-> This is necessary because packaging phase writes the `MANIFEST.MF` file into `target/classes` directory which triggers a recompilation of the main class *for the next submodule* in the reactor phase.
-> For a single module project, this `-Dmaven.main.skip` is not needed.
-> If you do need to compile the main class, you can run `mvn compile` again.
 
 2. Introspect
 ```bash
-java -javaagent:<path-to-classport-agent-jar>=<name-of-the-project>,<path-to-output-dir>,dependency -jar <path-to-jar-of-the-target-app> [optional-args-of-the-target-app]
+java -javaagent:classport-instr-agent/target/classport-instr-agent-0.1.0-SNAPSHOT.jar=<name-of-the-project>,<path-to-output-dir>,dependency -jar <path-to-jar-of-the-target-app> [optional-args-of-the-target-app]
 ```
 Note:
 - `name-of-the-project` can be any name and it is used to build the name of the output file.
 - `path-to-output-dir` must be a path of an existing folder
 
 ### Example of usage
-Run the following command from the root folder of Classport
+Run the following command from the root folder of Classport to try out the example.
+Or you may also see the test under [EmbeddingMojoIT.java](./maven-plugin/src/test/java/io/github/project/classport/plugin/it/EmbeddingMojoIT.java).
 
 ```bash
 cd resources/simple-app-monitoring
-mvn clean
 
 # Embed
-mvn compile io.github.project:classport-maven-plugin:0.1.0-SNAPSHOT:embed
-mvn package -Dmaven.repo.local=classport-files -DskipTests
-> single module project so we do not need to skip the main class compilation.
+mvn clean package -DskipTests -Pembed
 
 # Introspect
 mkdir output