svn commit: r1598421 - /commons/proper/weaver/trunk/src/site/markdown/index.md

[mb...@apache.org]

Author: mbenson
Date: Thu May 29 21:48:27 2014
New Revision: 1598421

URL: http://svn.apache.org/r1598421
Log:
Add Gary's question as a FAQ

Modified:
    commons/proper/weaver/trunk/src/site/markdown/index.md

Modified: commons/proper/weaver/trunk/src/site/markdown/index.md
URL: http://svn.apache.org/viewvc/commons/proper/weaver/trunk/src/site/markdown/index.md?rev=1598421&r1=1598420&r2=1598421&view=diff
==============================================================================
--- commons/proper/weaver/trunk/src/site/markdown/index.md (original)
+++ commons/proper/weaver/trunk/src/site/markdown/index.md Thu May 29 21:48:27 2014
@@ -152,6 +152,13 @@ current configuration is incompatible wi
          [EPL](http://eclipse.org/legal/epl-v10.html) which can be
          considered less permissive than the Apache license. Choice is
          A Good Thing.
+* *Q*: What is the relationship between Commons Weaver and ASM/Javassist/CGLIB?
+
+    *A*: Rather than being an _alternative_ to these technologies, Commons
+         Weaver can be thought of as providing a structured environment in
+         which these technologies can be put to use. I.e., the bytecode
+         modifications made by a given `Weaver` implementation would typically
+         be done with one of these (or comparable) libraries.
 
 [mvnplugin]: commons-weaver-maven-plugin/plugin-info.html
 [antlib]: commons-weaver-antlib-parent/commons-weaver-antlib/index.html