svn commit: r1400733 - /maven/plugins/trunk/maven-dependency-plugin/src/site/fml/faq.fml

[hb...@apache.org]

Author: hboutemy
Date: Sun Oct 21 22:27:25 2012
New Revision: 1400733

URL: http://svn.apache.org/viewvc?rev=1400733&view=rev
Log:
[MDEP-124] added a FAQ entry for wrong unused dependency when not detected at bytecode level

Modified:
    maven/plugins/trunk/maven-dependency-plugin/src/site/fml/faq.fml

Modified: maven/plugins/trunk/maven-dependency-plugin/src/site/fml/faq.fml
URL: http://svn.apache.org/viewvc/maven/plugins/trunk/maven-dependency-plugin/src/site/fml/faq.fml?rev=1400733&r1=1400732&r2=1400733&view=diff
==============================================================================
--- maven/plugins/trunk/maven-dependency-plugin/src/site/fml/faq.fml (original)
+++ maven/plugins/trunk/maven-dependency-plugin/src/site/fml/faq.fml Sun Oct 21 22:27:25 2012
@@ -78,5 +78,14 @@ under the License.
         </p>
       </answer>
     </faq>
+    <faq id="unused">
+      <question>Why does my dependency analysis report <code>Unused declared dependencies</code>?</question>
+      <answer><p>
+        By default, dependency analysis is done at bytecode level: anything that doesn't get into bytecode isn't detected.
+        This is the case, for example, of constants, annotations with source retention policy, or javadoc links.</p>
+        <p>If the only use of a dependency consists of such undetected constructs, the dependency is analyzed
+        as unused. Since 2.6, you can force use report with <code>usedDependencies</code> parameter.</p>
+      </answer>
+    </faq>
   </part>
 </faqs>