You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tomee.apache.org by vi...@apache.org on 2011/12/15 18:11:47 UTC

svn commit: r1214870 - /openejb/site/trunk/content/dev/source-code.mdtext

Author: vishwanathk
Date: Thu Dec 15 17:11:47 2011
New Revision: 1214870

URL: http://svn.apache.org/viewvc?rev=1214870&view=rev
Log:
Tomee-49 Correct svn url and alignment

Modified:
    openejb/site/trunk/content/dev/source-code.mdtext

Modified: openejb/site/trunk/content/dev/source-code.mdtext
URL: http://svn.apache.org/viewvc/openejb/site/trunk/content/dev/source-code.mdtext?rev=1214870&r1=1214869&r2=1214870&view=diff
==============================================================================
--- openejb/site/trunk/content/dev/source-code.mdtext (original)
+++ openejb/site/trunk/content/dev/source-code.mdtext Thu Dec 15 17:11:47 2011
@@ -1,4 +1,6 @@
 Title: Source Code
+
+Title: Source Code
 <a name="SourceCode-Browsing"></a>
 # Browsing
 
@@ -9,21 +11,21 @@ You can browse the source code via the [
 # Downloading
 
 You can download (aka checkout) the sources of Apache OpenEJB with
-Subversion client using the following URL [http://svn.apache.org/repos/asf/openejb/trunk/openejb3](http://svn.apache.org/repos/asf/openejb/trunk/openejb3)
+Subversion client using the following URL [http://svn.apache.org/repos/asf/openejb/trunk/openejb](http://svn.apache.org/repos/asf/openejb/trunk/openejb)
 .
 
 Performing the checkout from the command line using the subversion client
 is as easy as executing the following command:
-> $ svn co [http://svn.apache.org/repos/asf/openejb/trunk/openejb3](http://svn.apache.org/repos/asf/openejb/trunk/openejb3)
+> $ svn co [http://svn.apache.org/repos/asf/openejb/trunk/openejb](http://svn.apache.org/repos/asf/openejb/trunk/openejb)
 
 If you are experiencing problems with errors like "400 Bad Request
 (http://svn.apache.org)", try using:
-> $ svn co [https://svn.apache.org/repos/asf/openejb/trunk/openejb3](https://svn.apache.org/repos/asf/openejb/trunk/openejb3)
+> $ svn co [https://svn.apache.org/repos/asf/openejb/trunk/openejb](https://svn.apache.org/repos/asf/openejb/trunk/openejb)
 
 or alternatively with Apache Maven 2 or later:
 > mvn scm:checkout
-> -DconnectionUrl=scm:svn:http://svn.apache.org/repos/asf/openejb/trunk/openejb3
-> -DcheckoutDirectory=openejb3
+> -DconnectionUrl=scm:svn:http://svn.apache.org/repos/asf/openejb/trunk/openejb
+> -DcheckoutDirectory=openejb
 
 It's not yet known how to see the progress of the checkout as mvn
 scm:checkout checks out the sources non-interactively. It's worth to know
@@ -47,11 +49,15 @@ All builders are available [from the pag
 
 To build the code, you'll need to grab a copy of [Apache Maven](http://maven.apache.org)
  version 2.0.4 or later.  The standard build command is as follows:
-> $ cd openejb3
-> $ mvn -Dassemble clean install
+
+<pre><code>
+$ cd openejb3
+$ mvn -Dassemble clean install
 or alternatively when on Unix-like OSes
-> $ cd openejb3
-> $ mvn \-o \-Dmaven.\{test,itest\}.skip \-Dassemble clean install
+$ cd openejb3
+$ mvn \-o \-Dmaven.\{test,itest\}.skip \-Dassemble clean install
+</code></pre>
+
 Running with the *assemble* option turned on enables a profile that builds
 OpenEJB's assemblies (distros). They live in *assembly* directory. You can
 remove it from the command line if you're not interested in them - just
@@ -69,7 +75,7 @@ on MacOS and Unices or _set MAVEN_OPTS=-
 {info}
 
 The output of that command should end with "BUILD SUCCESSFUL"
-
+<pre><code>
     [INFO]
  ------------------------------------------------------------------------
     [INFO]
@@ -295,16 +301,18 @@ SUCCESS [0.271s]
  Final Memory: 153M/338M
     [INFO]
  ------------------------------------------------------------------------
-
+</code></pre>
 
 <a name="SourceCode-Running"></a>
 # Running
 
+
 Provided you have successfully built OpenEJB with the assemble option
 turned on, you can find assemblies in the *target* directories beneath the
 *assembly* directory of each custom assembly. Go to the assembly directory
 and have a look at its content.
 
+<pre><code>
     jacek@devmac /Users/jacek/oss/openejb3/assembly
     $ ls -l
     total 8
@@ -319,7 +327,7 @@ openejb-itests-standalone-client
     -rw-r--r--   1 jacek  staff  1726 Jun  1 22:51 pom.xml
     drwxr-xr-x   4 jacek  staff   136 Jun 19 20:46 target
     drwxr-xr-x   4 jacek  staff   136 Jun  1 22:51 test
-
+</code></pre>
 The most common choice is to go to openejb-standalone which is exactly what
 the name stands for - it lets you get OpenEJB up and running from a command
 line with no additional configuration - in other words you can play with
@@ -327,6 +335,7 @@ your EJBs right away. Looking at the *op
 reveals the tar.gz'ed and zip'ed distributions. Unpack one and give it a
 go.
 
+<pre><code>
     jacek@devmac /Users/jacek/oss/openejb3/assembly/openejb-standalone/target
     $ jar -xvf openejb-3.2-SNAPSHOT.zip
      created: openejb-3.2-SNAPSHOT/
@@ -371,14 +380,14 @@ getConfigResources
       telnet	       127.0.0.1       4202  
     -------
     Ready!
-
+</code></pre>
 
 There's another, slightly less error-prone approach using a shell script -
 _try.sh_ - that's tailor-made for that particular task - running OpenEJB 3
 right after it's been built locally. No need to remember these
 aforementioned steps but the mere name of the script itself
 
-
+<pre><code>
     jacek@devmac /Users/jacek/oss/openejb3/assembly/openejb-standalone
     $ ./try.sh
     x openejb-3.2-SNAPSHOT/lib/xmlsec-1.4.3.jar
@@ -432,7 +441,7 @@ below.
     -------
     Ready!
 
-
+</code></pre>
 The old 2 finger salute - Ctrl-C - stops the OpenEJB instance.
 
 
@@ -446,25 +455,25 @@ Debug without suspending, so that the se
 debugged at any point you wish. If you are in the directory where you
 extracted the assembly to, just issue the following command...
 
-
+<pre><code>
     jacek@devmac
 Users/jacek/oss/openejb3/assembly/openejb-standalone/target/openejb-3.2-SNAPSHOT
     $ OPENEJB_OPTS="-Xdebug
 -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=8001"
 ./bin/openejb start
-
+</code></pre>
 
 Debug and suspend until a debugger has been attached. This is helpful if
 the code that is to be debugged happens to be some of the startup code. The
 following command would achieve this mode...
 
-
+<pre><code>
     jacek@devmac
 Users/jacek/oss/openejb3/assembly/openejb-standalone/target/openejb-3.2-SNAPSHOT
     $ OPENEJB_OPTS="-Xdebug
 -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=8001"
 ./bin/openejb start
-
+</code></pre>
 
 Once either mode is started, just attach your favourite development IDE or
-debugger, and away you go.
+debugger, and away you go.
\ No newline at end of file