CVS: jcontainer/loom/site/xdocs porting-guide.xml,1.5,1.6

Peter Donald <pdonald-yCVjj/[email protected]> Sat, 29 Nov 2003 01:25:17 -0600
Newsgroups gmane.comp.java.jcontainer.cvs
Message-ID <[email protected]>
Update of /cvsroot/jcontainer/jcontainer/loom/site/xdocs
In directory hogshead.codehaus.org:/tmp/cvs-serv20631/site/xdocs

Modified Files:
	porting-guide.xml 
Log Message:
Upgrade to DNA rc2 and MetaClass rc2


Index: porting-guide.xml
===================================================================
RCS file: /cvsroot/jcontainer/jcontainer/loom/site/xdocs/porting-guide.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -d -r1.5 -r1.6
--- porting-guide.xml	8 Nov 2003 10:02:08 -0000	1.5
+++ porting-guide.xml	29 Nov 2003 07:25:14 -0000	1.6
@@ -6,22 +6,22 @@
 	</properties>
 
 	<body>
-	
+
 	<section name="Porting Phoenix 4.0.x applications">
 		<p>
 		    Loom 1.0 supports applications running in Phoenix 4.0.x releases,
-		    provided that the sar is built using the 
+		    provided that the sar is built using the
 		    <a href="/plugins/maven-sar/">Maven Sar Plugin</a>
 		    provided by Loom and the appropriate libraries are bundles in the sar.
 		</p>
 	<subsection name="Creating a Loom Sar">
 		<p>
-			Since the generation of metaclass descriptors is more generic in 
+			Since the generation of metaclass descriptors is more generic in
 			Loom compared with Phoenix, but still fully compatible with it,
 			users can deploy applications running in Phoenix 4.0.x by simply
 			regenerating from the Java source the descriptors using the Maven Sar Plugin.
-		</p>		
-		<p> 
+		</p>
+		<p>
 			To create a sar, using the <a href="/plugins/maven-sar/">Maven Sar Plugin</a>
 			simply add the dependency to your Maven project
 <source>
@@ -31,13 +31,18 @@
     <artifactId>maven-sar-plugin</artifactId>
     <version>[plugin-version]</version>
     <type>plugin</type>
-</dependency>			
+</dependency>
 ]]>
 </source>
-			set in your project.properties
+			And then make sure that the sar:metagenerate is invoked after java
+            compilation by adding the following to a custom maven.xml.
 <source>
-maven.sar.metagenerate=true
-</source>			
+<![CDATA[
+    <postGoal name="java:compile">
+        <attainGoal name="sar:metagenerate"/>
+    </postGoal>
+]]>
+</source>
 			and execute
 <source>
 maven sar
@@ -46,12 +51,12 @@
 	</subsection>
 	<subsection name="Comparison of libraries bundled">
 		<p>
-			Compared to the Phoenix 4.0.x distribution, in the Loom 1.0 distribution 
-			some of the libraries in the <code>lib/</code> directory 
-			have been removed as they are not used by the container. 
-			If your app uses any of the excluded libraries, 
-			you simply need to bundle them with the sar.  
-		</p>		
+			Compared to the Phoenix 4.0.x distribution, in the Loom 1.0 distribution
+			some of the libraries in the <code>lib/</code> directory
+			have been removed as they are not used by the container.
+			If your app uses any of the excluded libraries,
+			you simply need to bundle them with the sar.
+		</p>
 		<p>
 			Loom 1.0 comes with a lean set of libraries:
 <source>
@@ -61,7 +66,7 @@
 log4j
 mx4j-jmx
 phoenix-client
-</source>		
+</source>
 		</p>
 		<p>
 			Phoenix 4.0.x ships a bigger set of libraries:
@@ -89,10 +94,10 @@
 xalan
 xercesImpl
 xml-apis
-</source>		
+</source>
 		</p>
 	</subsection>
 	</section>
-	
+
 	</body>
 </document>