[Clirr-devel] CVS: clirr/core/src/site/xdoc anttask.xml, 1.1, 1.2 runcli.xml, 1.1, 1.2

[Lars K. <lk...@us...>]

Update of /cvsroot/clirr/clirr/core/src/site/xdoc
In directory ddv4jf1.ch3.sourceforge.com:/tmp/cvs-serv25508/src/site/xdoc

Modified Files:
	anttask.xml runcli.xml 
Log Message:
fixed name of uberjar

Index: anttask.xml
===================================================================
RCS file: /cvsroot/clirr/clirr/core/src/site/xdoc/anttask.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- anttask.xml	6 Oct 2008 22:08:23 -0000	1.1
+++ anttask.xml	6 Oct 2008 22:12:36 -0000	1.2
@@ -28,8 +28,8 @@
 <target name="checkbinarycompatibility" depends="build">
 
   <!-- buildtools.classpath should either contain
-        clirr-core-uber.jar or alternatively
-        clirr-core.jar and the libraries it depends on -->
+        clirr-core-@VE...@-a... or alternatively
+        clirr-core-@VERSION@.jar and the libraries it depends on -->
 
   <taskdef
         classpathref="buildtools.classpath"

Index: runcli.xml
===================================================================
RCS file: /cvsroot/clirr/clirr/core/src/site/xdoc/runcli.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- runcli.xml	6 Oct 2008 22:08:23 -0000	1.1
+++ runcli.xml	6 Oct 2008 22:12:36 -0000	1.2
@@ -13,7 +13,7 @@
         executable jar file. Clirr can then be run from a commandline
         via the command:
         <code>
-          java -jar clirr-core-@VE...@-u...
+          java -jar clirr-core-@VE...@-a...
         </code>
         Running clirr with no command-line arguments will display the
         available options.