[jboss-svn-commits] JBL Code SVN: r11696 - labs/jbossrules/trunk.

[jboss-svn-commits at lists.jboss.org]

Author: mark.proctor at jboss.com
Date: 2007-05-04 20:25:25 -0400 (Fri, 04 May 2007)
New Revision: 11696

Modified:
   labs/jbossrules/trunk/README.txt
   labs/jbossrules/trunk/README_DEPENDENCIES.txt
Log:
-added line-wrap at 80 cols on *.txt files

Modified: labs/jbossrules/trunk/README.txt
===================================================================
--- labs/jbossrules/trunk/README.txt	2007-05-04 19:14:02 UTC (rev 11695)
+++ labs/jbossrules/trunk/README.txt	2007-05-05 00:25:25 UTC (rev 11696)
@@ -1,13 +1,25 @@
 Welcome to Drools
 -----------------
 
-Drools uses maven to build the system. There are two profiles available which enable the associated modules "documentation" and "eclipse"; this enables quicker building of the core modules for developers. The eclipse profile will download eclipse into the drools-eclipse folder, which is over 100MB download, however this only needs to be done once; if you wish you can move that eclipse download into another location and specify it with -DlocalEclipseDrop=/folder/jboss-rules/local-eclipse-drop-mirror. 
+Drools uses maven to build the system. There are two profiles available which
+enable the associated modules "documentation" and "eclipse"; this enables
+quicker building of the core modules for developers. The eclipse profile will
+download eclipse into the drools-eclipse folder, which is over 100MB download,
+however this only needs to be done once; if you wish you can move that eclipse
+download into another location and specify it with
+-DlocalEclipseDrop=/folder/jboss-rules/local-eclipse-drop-mirror.
 
-The following builds all the jars, the documentation and the eclipse zip with a local folder specified to avoid downloading eclipse
-mvn -Declipse=true -Ddocumentation=true clean install -DlocalEclipseDrop=/folder/jboss-rules/local-eclipse-drop-mirror
+The following builds all the jars, the documentation and the eclipse zip with a
+local folder specified to avoid downloading eclipse:
+ mvn -Declipse=true -Ddocumentation=true clean install 
+     -DlocalEclipseDrop=/folder/jboss-rules/local-eclipse-drop-mirror
 
-You can produce distribution builds, which puts everything into zips, as follows:
-mvn -Declipse=true -Ddocumentation=true clean install -DlocalEclipseDrop=/folder/jboss-rules/local-eclipse-drop-mirror
-mvn -Ddocumentation -Declipse -Dmaven.test.skip package javadoc:javadoc assembly:assembly -DlocalEclipseDrop=/folder/jboss-rules/local-eclipse-drop-mirror
+You can produce distribution builds, which puts everything into zips, as
+follows:
+mvn -Declipse=true -Ddocumentation=true clean install
+    -DlocalEclipseDrop=/folder/jboss-rules/local-eclipse-drop-mirror
+mvn -Ddocumentation -Declipse -Dmaven.test.skip package javadoc:javadoc
+     assembly:assembly -DlocalEclipseDrop=/folder/jboss-rules/local-eclipse-drop-mirror
 
-Note that install must be done first as javadoc:javadoc won't work unless the jars are in the local maven repo, but the tests can be skipped on the second run.
\ No newline at end of file
+Note that install must be done first as javadoc:javadoc won't work unless the
+jars are in the local maven repo, but the tests can be skipped on the second run.
\ No newline at end of file

Modified: labs/jbossrules/trunk/README_DEPENDENCIES.txt
===================================================================
--- labs/jbossrules/trunk/README_DEPENDENCIES.txt	2007-05-04 19:14:02 UTC (rev 11695)
+++ labs/jbossrules/trunk/README_DEPENDENCIES.txt	2007-05-05 00:25:25 UTC (rev 11696)
@@ -1,4 +1,5 @@
-This is a summary of what jars you may need in your situation. Abbreviated names have been used (only the first part of the jar name).
+This is a summary of what jars you may need in your situation. Abbreviated names
+have been used (only the first part of the jar name).
 
 CORE RUNTIME
 Runtime assumes that you are "compiling" rules using drools-compiler.
@@ -6,18 +7,23 @@
     * drools-core - the rule engine itself.
     * mvel14-1.2beta16
     * optional packages:
-          o xpp3-1.1.3.4.O, xstream-1.1.3 - if you are using the file based audit feature
+          o xpp3-1.1.3.4.O, xstream-1.1.3 - if you are using the file based
+audit feature
 
-Note you can use the drools-core stand-alone if you are compiling "outside" your runtime application, and deploying serialized Package or RuleBase? objects.
+Note you can use the drools-core stand-alone if you are compiling "outside" your
+runtime application, and deploying serialized Package or RuleBase? objects.
 
 COMPILER - rule assembly time
-Rule compiler takes rules in some textual format and prepares binary Packages of rules for deployment. This depends on the CORE RUNTIME.
+Rule compiler takes rules in some textual format and prepares binary Packages of
+rules for deployment. This depends on the CORE RUNTIME.
 
     * drools-core
     * drools-compiler - the rule compiler itself.
     * antlr3-3.0b7
-    * xerces-2.4.0, xml-apis-1.0.b2 - only if you are using XML rules, if DRL only, can skip this.
-    * eclipse-jdt-core-3.2.1.v_677_R32x - only if you want to compile with eclipse
+    * xerces-2.4.0, xml-apis-1.0.b2 - only if you are using XML rules, if DRL
+only, can skip this.
+    * eclipse-jdt-core-3.2.1.v_677_R32x - only if you want to compile with
+eclipse
     * janino-2.5.6 - only if you want to compile with janino
 
 JSR-94
@@ -33,13 +39,18 @@
 
     * drools-core
     * drools-compiler - required as rules are generated and compiled
-    * drools-decisiontables - contains the spreadsheet compiler for both XLS and CSV
+    * drools-decisiontables - contains the spreadsheet compiler for both XLS and
+CSV
     * jxl-2.4.2 (jexcelapi) - for parsing Excel spreadsheets.
 
-The most common use case is for COMPILER - this allows rules to be loaded from their source form, 
-and includes the runtime engine of course. 
-For example, if you wanted to be able to load rules from a drl source you would need: drools-core and the COMPILER jars mentioned above 
-(not xerces, and not xml-apis). You will only need optional core jars if you are using those features.
+The most common use case is for COMPILER - this allows rules to be loaded from
+their source form,
+and includes the runtime engine of course.
+For example, if you wanted to be able to load rules from a drl source you would
+need: drools-core and the COMPILER jars mentioned above
+(not xerces, and not xml-apis). You will only need optional core jars if you are
+using those features.
 
-When building from source, the dependencies are managed by maven. 
-In each module, there is a pom.xml file that lists the exact dependencies and exact version numbers.
+When building from source, the dependencies are managed by maven.
+In each module, there is a pom.xml file that lists the exact dependencies and
+exact version numbers.