You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@avalon.apache.org by mc...@apache.org on 2003/08/19 16:23:56 UTC
cvs commit: avalon-sandbox/merlin/merlin-platform/tutorials/hello README.txt
mcconnell 2003/08/19 07:23:56
Modified: merlin/merlin-platform/tutorials/hello README.txt
Log:
Enhancements.
Revision Changes Path
1.2 +11 -5 avalon-sandbox/merlin/merlin-platform/tutorials/hello/README.txt
Index: README.txt
===================================================================
RCS file: /home/cvs/avalon-sandbox/merlin/merlin-platform/tutorials/hello/README.txt,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- README.txt 17 Aug 2003 16:31:25 -0000 1.1
+++ README.txt 19 Aug 2003 14:23:56 -0000 1.2
@@ -7,9 +7,13 @@
create a jar file under the target directory named
merlin-hello-tutorial-1.0.jar. The jar file contains a single
component and a bundled block.xml deployment descriptor. To
-see Merlin in action, execute Merlin and give it the jar file
-as the deployment argument. Merlin will grab the block.xml
-packaged in the jar file and use this to execute the demo.
+see Merlin in action, execute Merlin and give it either the
+jar file of the target/classes directory as the deployment
+argument.
+
+$ merlin target\classes -execute
+
+Or:
$ merlin target\merlin-hello-tutorial-1.0.jar -execute
@@ -19,8 +23,10 @@
until we forced termination using ^C.
To get an idea of what is happening behing the scenes you can
-use the debug flag:
+override the logging priorities using a configuration override
+argument. In addition, the -debug CLI parameter presents a
+summary of the resources pulling together to handle deployment:
-$ merlin target\merlin-hello-tutorial-1.0.jar -execute -debug
+$ merlin target\classes -execute -debug -config conf\config.xml
---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@avalon.apache.org
For additional commands, e-mail: cvs-help@avalon.apache.org