Changes between Version 372 and Version 373 of WikiStart

Timestamp:

01/26/21 14:45:24 (4 years ago)

Author:

wouter

Comment:

--

WikiStart

@@ -865 +865 @@
 
 = Stand-alone Running =
-For stand-alone running you need to have the following available in your project space (this includes the maven dependencies you have set for your project)
-* The parties you want to run (in compiled form) must be in your classpath
+For stand-alone running you need to 
+* download the stand-alone runner, eg download from [http://artifactory.ewi.tudelft.nl/artifactory/libs-release/geniusweb/simplerunner/ geniusweb artifactory] select latest version simplerunner-<latestversion>-jar-with-dependencies.jar. Easiest is to clone the project with {{{svn co https://tracinsy.ewi.tudelft.nl/pub/svn/GeniusWeb/simplerunner}}} 
+* The parties you want to run (in compiled form) must be in your classpath. Typically by adding them to the pom of the stand-alone runner.
 * The profiles you want to provide to the parties (alternatively you can refer to a profile on a running profile server)
 * A settings.json file containing the [source:/protocol/src/main/java/geniusweb/protocol/session SessionSettings] eg SAOP Settings. [source:/simplerunner/src/test/resources/settings.json view example file]. 
-* a simple stand-alone runner, eg download from [http://artifactory.ewi.tudelft.nl/artifactory/libs-release/geniusweb/simplerunner/ geniusweb artifactory] select latest version simplerunner-<latestversion>-jar-with-dependencies.jar.
 
 A complete example is available of [source:/simplerunner simplerunner here]
@@ -876 +876 @@
 
 == Running ==
-Make sure your parties are in the java classpath.
-
-A stand-alone runner can now be started as follows (using the example, set your working directory to the root of the simplerunner project )
+
+
+A stand-alone runner can now be started as follows 
+
+run {{{geniusweb.simplerunner.NegoRunner}}}  in  Eclipse 
+with {{{src/test/resources/settings.json}}} as argument.
+
+or from the command line which is a bit more complicated:
 {{{
 java -jar simplerunner...with-dependencies.jar src/test/resources/settings.json
@@ -909 +914 @@
 == Debugging with stand-alone runner
  * Using a stand-alone runner (normal Eclipse for Java developers, no EE needed)
- * Have your party's source code in the Eclipse workspace
- * Clone the simplerunner into your workspace {{{svn co https://tracinsy.ewi.tudelft.nl/pub/svn/GeniusWeb/simplerunner}}}
- * Edit the src/test/resource/settings.json file in the simplerunner to match your party
+ * Set up a stand-alone run as described in #Stand-aloneRunning
  * Place a breakpoint in your party where you want to debug.
- * Create a debug configuration for NegoRunner with some customized settings: 
-  * Add <dependency> for party to the standalone pom. Something like 
-    {{{
-                <dependency>
-                        <groupId>collabai.team3</groupId>
-                        <artifactId>teamXXXparty</artifactId>
-                        <version>X.Y.Z</version> <!--Fill in correct version -->
-                </dependency>
-
-    }}} 
-  * Set {{{src/test/resources/settings.json}}} as program argument 
  * Run the debug configuration 
  * Eclipse will halt server execution and switch to debugging when it hits your breakpoint