From a02bb884f66d83e9fc04b2b089effc285ea2783d Mon Sep 17 00:00:00 2001
From: Uwe Schindler <uwe@thetaphi.de>
Date: Thu, 10 Sep 2015 11:07:46 +0200
Subject: [PATCH] Update Maven docs about new lifecycle phase.

---
 src/main/java/de/thetaphi/forbiddenapis/maven/CheckMojo.java   | 3 +++
 .../java/de/thetaphi/forbiddenapis/maven/TestCheckMojo.java    | 3 +++
 2 files changed, 6 insertions(+)

diff --git a/src/main/java/de/thetaphi/forbiddenapis/maven/CheckMojo.java b/src/main/java/de/thetaphi/forbiddenapis/maven/CheckMojo.java
index 92768d97..8265bebd 100644
--- a/src/main/java/de/thetaphi/forbiddenapis/maven/CheckMojo.java
+++ b/src/main/java/de/thetaphi/forbiddenapis/maven/CheckMojo.java
@@ -31,6 +31,9 @@
  * <p>
  * This Mojo exists since version 1.2, replacing the old <code>forbiddenapis:forbiddenapis</code> goal.
  * <em>In most cases its enough to rename the goal on update, the older v1.0 properties are still available.</em>
+ * <p>
+ * Since version 2.0 this Mojo defaults to run in the {@code 'verify'} lifecycle phase, before it was done in
+ * {@code 'process-classes'} phase, which caused problems for some users (especially debugging tests).
  * @since 1.2
  */
 @Mojo(name = "check", threadSafe = true, requiresProject = true, requiresDependencyResolution = ResolutionScope.COMPILE, defaultPhase = LifecyclePhase.VERIFY)
diff --git a/src/main/java/de/thetaphi/forbiddenapis/maven/TestCheckMojo.java b/src/main/java/de/thetaphi/forbiddenapis/maven/TestCheckMojo.java
index 105ddd86..f7f671f1 100644
--- a/src/main/java/de/thetaphi/forbiddenapis/maven/TestCheckMojo.java
+++ b/src/main/java/de/thetaphi/forbiddenapis/maven/TestCheckMojo.java
@@ -28,6 +28,9 @@
  * Mojo to check if no project generated class files (test scope) contain calls to forbidden APIs
  * from the project classpath and a list of API signatures (either inline or as pointer to files or bundled signatures).
  * At least one signature must be given, using any of the corresponding optional parameters.
+ * <p>
+ * Since version 2.0 this Mojo defaults to run in the {@code 'verify'} lifecycle phase, before it was done in
+ * {@code 'process-test-classes'} phase, which caused problems for some users (especially debugging tests).
  * @since 1.2
  */
 @Mojo(name = "testCheck", threadSafe = true, requiresProject = true, requiresDependencyResolution = ResolutionScope.TEST, defaultPhase = LifecyclePhase.VERIFY)