commons-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r1546219 - /commons/proper/weaver/trunk/src/site/markdown/
Date Wed, 27 Nov 2013 22:42:58 GMT
Author: mbenson
Date: Wed Nov 27 22:42:57 2013
New Revision: 1546219

expand documentation with invocation examples


Modified: commons/proper/weaver/trunk/src/site/markdown/
--- commons/proper/weaver/trunk/src/site/markdown/ (original)
+++ commons/proper/weaver/trunk/src/site/markdown/ Wed Nov 27 22:42:57 2013
@@ -17,15 +17,100 @@ specific language governing permissions 
 under the License.
-# Commons Weaver
+# Apache Commons Weaver
-Provides a general framework for the application of transformations
-to compiled Java bytecode. Commons Weaver provides:
+Provides a general framework for the application of
+transformations to compiled Java bytecode. It consists of:
-* [Core Framework](commons-weaver/index.html)
-* [Weaver Modules](commons-weaver-modules-parent/index.html)
-* [Maven Plugin] (commons-weaver-maven-plugin/plugin-info.html)
-* [Antlib] (commons-weaver-antlib-parent/commons-weaver-antlib/index.html)
+## Core Framework
+The [Commons Weaver Core](commons-weaver/index.html)
+defines a "weaver module" service provider interface (SPI) as well as
+the facilities that use the Java `ServiceLoader` to discover and invoke
+defined weaver modules for simple filesystem-based bytecode weaving.
+## Weaver Modules
+A number of [Weaver Modules](commons-weaver-modules-parent/index.html)
+are provided by the Commons Weaver project.
+Typically a weaver module may respect a set of configuration
+properties which should be documented along with that module.
+## Integration
+The weaver module(s) applicable to your codebase should be available
+on the classpath of whatever Java-based processing mechanism you select.
+Your responsibilities are to:
+ - trigger weave processing in some way
+ - make the desired weaver module(s) available for processing
+ - (optionally) provide configuration properties for applicable modules
+There are two provided mechanisms for invoking Weaving facilities:
+### Maven Plugin
+The [Commons Weaver plugin for Apache Maven][mvnplugin] aims to integrate
+Weaver as smoothly as possible for Maven users. Here is an example
+of configuring the `privilizer` module:
+      <plugin>
+        <groupId>org.apache.commons</groupId>
+        <artifactId>commons-weaver-maven-plugin</artifactId>
+        <version>${commons.weaver.version}</version>
+        <configuration>
+          <weaverConfig>
+            <privilizer.accessLevel>${privilizer.accessLevel}</privilizer.accessLevel>
+            <privilizer.policy>${privilizer.policy}</privilizer.policy>
+            <privilizer.verify>${privilizer.verify}</privilizer.verify>
+          </weaverConfig>
+        </configuration>
+        <executions>
+          <execution>
+            <goals>
+              <goal>prepare</goal>
+              <goal>weave</goal>
+            </goals>
+          </execution>
+        </executions>
+        <dependencies>
+          <dependency>
+            <groupId>org.apache.commons</groupId>
+            <artifactId>commons-weaver-privilizer-api</artifactId>
+            <version>${commons.weaver.version}</version>
+          </dependency>
+          <dependency>
+            <groupId>org.apache.commons</groupId>
+            <artifactId>commons-weaver-privilizer</artifactId>
+            <version>${commons.weaver.version}</version>
+          </dependency>
+        </dependencies>
+      </plugin>
+### Antlib
+The [Commons Weaver Antlib][antlib] provides tasks and types to
+facilitate the integration of Commons Weaver into your Apache Ant-based
+build process. Here the user will make the `commons-weaver` `jar`,
+along with the `jar` files of the desired modules, available to
+the Ant build using one of the various mechanisms supported. More
+information on this is available [here][antxt]. Having done this the
+basic approach will be to parameterize one of the provided tasks
+(`clean`|`weave`) with a `settings` element. If both `weave` and `clean`
+tasks are used, defining a [reference][antref] to the `settings` object
+and referencing it using the `settingsref` attribute is recommended, as
+seen here:
+      <settings id="weavesettings"
+                target="target/classes"
+                classpathref="maincp">
+        <properties>
+          <privilizer.accessLevel>${privilizer.accessLevel}</privilizer.accessLevel>
+          <privilizer.policy>${privilizer.policy}</privilizer.policy>
+          <privilizer.verify>${privilizer.verify}</privilizer.verify>
+        </properties>
+      </settings>
+      <clean settingsref="weavesettings" />
+      <weave settingsref="weavesettings" />
+Multiple weaving targets (e.g. `main` vs. `test`) are of course woven
+using different `settings`.
@@ -38,3 +123,8 @@ to compiled Java bytecode. Commons Weave
          [EPL]( which can be
          considered less permissive than the Apache license. Choice is
          A Good Thing.
+[mvnplugin]: commons-weaver-maven-plugin/plugin-info.html
+[antlib]: commons-weaver-antlib-parent/commons-weaver-antlib/index.html

View raw message