Author: buildbot
Date: Sat Nov 2 06:23:18 2013
New Revision: 885168
Log:
Staging update by buildbot for mina
Modified:
websites/staging/mina/trunk/content/ (props changed)
websites/staging/mina/trunk/content/mina-project/developper-guide.html
websites/staging/mina/trunk/content/mina-project/documentation.html
Propchange: websites/staging/mina/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Sat Nov 2 06:23:18 2013
@@ -1 +1 @@
-1518639
+1538147
Modified: websites/staging/mina/trunk/content/mina-project/developper-guide.html
==============================================================================
--- websites/staging/mina/trunk/content/mina-project/developper-guide.html
(original)
+++ websites/staging/mina/trunk/content/mina-project/developper-guide.html Sat
Nov 2 06:23:18 2013
@@ -139,172 +139,196 @@
<h1 id="building-mina">Building MINA</h1>
<DIV class="note" markdown="1">
Please read <a href="http://www.apache.org/dev/"; class="external-link"
rel="nofollow">the Developer Infrastructure Information</a> if you haven't yet
before you proceed.
-</div>
-
-[TOC]
-
-# Checking out the code
-
-You need [Subversion](http://subversion.tigris.org) to check out the source
code from our source code repository, and [Maven(http://maven.apache.org/)
2.2.1 to build the source code (Building with Maven 3.0 will also work). The
following example shows how to build [the current stable branch
(2.0.7)](http://svn.apache.org/viewvc/mina/mina/tags/2.0.7/).
-
- $ svn co https://svn.apache.org/repos/asf/mina/mina/tags/2.0.7/ mina
- $ cd mina
- $ mvn -Pserial clean install # Build packages (JARs) for the
core API and other
- # extensions and install them to
the local Maven repository.
- $ mvn -Pserial site # Generate reports (JavaDoc and
JXR)
- $ mvn -Pserial package assembly:assembly # Generate a tarball (package
goal needed to fix an assembly plugin bug)
- $ mvn -Pserial eclipse:eclipse # Generate Eclipse project files
if you want
-
-Eclipse users:
-Don't forget to declare a classpath variable named M2_REPO, pointing to
`~/.m2/repository`, otherwise many links to existing jars will be broken.
-You can declare new variables in Eclipse in Windows -> Preferences... and
selecting Java -> Build Path -> Classpath Variables
-
-There are also other branches that might interest you:
-
-* trunk: [Where big changes take place
everyday](http://svn.apache.org/viewvc/mina/mina/trunk/) -
`http://svn.apache.org/repos/asf/mina/mina/trunk/`
-
-If you want to check out the source code of previous releases, you could try:
-
-* `http://svn.apache.org/repos/asf/mina/mina/tags/`
-
-# Coding Convention
-
-We follow [Sun's standard Java coding
convention](http://www.oracle.com/technetwork/java/javase/documentation/codeconvtoc-136057.html)
except that we always use spaces instead of tabs. Please download [the Eclipse
Java formatter settings file](ImprovedJavaConventions.xml) before you make any
changes to the code.
-
-This file is also available in the `/resources` directory.
-
-# Class header
-
-As class header we use :
-
- /**
- * Class desciption here.
- *
- * @author <a href="http://mina.apache.org";>Apache MINA Project</a>
- */
-
-The headers revisions tags are removed.
-
-# Working with Multiple Branches in One Eclipse Workspace
-
-Just running `mvn -Pserial eclipse:eclipse` won't allow you to import MINA
projects from more than one branches into one Eclipse workspace. You have to
rename all project names in the generated `.project` and `.classpath` files to
do that. Maven Eclipse plugin should provide an option that appends the
version number to the project name, but [this
issue](http://jira.codehaus.org/browse/MECLIPSE-189) is not being resolved yet.
Until this issue is resolved, please put the attached shell script files
((mvnroot) and (mvn-eclipse)) to your local path (e.g. `/usr/local/bin`) and
run `mvn-eclipse`.
-
- $ svn co https://svn.apache.org/repos/asf/mina mina
- $ cd mina/tags/2.0.7
- $ mvn-eclipse
- $ cd ../2.0.5
- $ mvn-eclipse
- $ cd ../../trunk
- $ mvn-eclipse
-
-Then `mvn eclipse:eclipse` command is executed internally, and the branch name
will be appended to all sub-module project files generated by Maven Eclipse
plugin.
-
-# Deploying Snapshots (Commiters Only)
-
-Before running Maven to deploy artifacts, *please make sure if your umask is
configured correctly*. Unless configured properly, other committers will
experience annoying 'permission denied' errors. If your default shell is
`bash`, please update your umask setting in the `~/.bashrc` file (create one if
it doesn't exist.) by adding the following line:
-
- umask 002
-
-Please note that you have to edit the correct `shrc` file. If you use `csh`,
then you will have to edit `~/.cshrc` file.
-
-Now you are ready to deploy the artifacts if you configured your umask
correctly.
+</DIV>
- $ svn co https://svn.apache.org/repos/asf/mina/tags/2.0.7 mina
- $ cd mina
- $ mvn -Pserial clean deploy site site:deploy # Make sure to run 'clean'
goal first to prevent side effects from your IDE.
+<div class="toc">
+<ul>
+<li><a href="#building-mina">Building MINA</a></li>
+<li><a href="#checking-out-the-code">Checking out the code</a></li>
+<li><a href="#coding-convention">Coding Convention</a></li>
+<li><a href="#class-header">Class header</a></li>
+<li><a href="#working-with-multiple-branches-in-one-eclipse-workspace">Working
with Multiple Branches in One Eclipse Workspace</a></li>
+<li><a href="#deploying-snapshots-commiters-only">Deploying Snapshots
(Commiters Only)</a></li>
+<li><a href="#releasing-a-point-release-committers-only">Releasing a Point
Release (Committers Only)</a><ul>
+<li><a href="#preparing-the-release-for-the-vote">Preparing the release for
the vote</a><ul>
+<li><a href="#step-0-building-mina">Step 0: Building MINA</a></li>
+<li><a href="#step-1-tagging-and-deploying">Step 1: Tagging and
Deploying</a></li>
+<li><a href="#step-2-processing-with-a-dry-run">step 2 : Processing with a dry
run</a></li>
+<li><a href="#step-3-processing-with-the-real-release">Step 3 : Processing
with the real release</a></li>
+<li><a href="#step-4-perform-the-release">Step 4 : perform the release</a></li>
+<li><a href="#step-5-closing-the-staging-release-on-nexus">Step 5 : closing
the staging release on nexus</a></li>
+</ul>
+</li>
+<li><a href="#voting-a-release">Voting a release</a><ul>
+<li><a href="#step-1-send-a-vote-mail-on-the-mailing-list">Step 1 : Send a
[VOTE] mail on the mailing list</a></li>
+<li><a href="#step-2-close-the-vote">Step 2 : Close the vote</a></li>
+<li><a href="#step-3-deploy-web-reports-javadoc-and-jxr">Step 3: Deploy Web
Reports (JavaDoc and JXR)</a></li>
+<li><a href="#step-4-wait-24-hours">Step 4: Wait 24 hours</a></li>
+<li><a href="#step-5-update-the-links-in-web-site">Step 5: Update the Links in
Web Site</a></li>
+<li><a href="#step-8-update-related-metadata-files">Step 8: Update related
metadata file(s)</a></li>
+<li><a href="#step-9-wait-another-24-hours">Step 9: Wait another 24
hours</a></li>
+<li><a href="#step-10-announce-the-new-release">Step 10: Announce the New
Release</a></li>
+</ul>
+</li>
+<li><a href="#creating-a-new-release-branch">Creating a New Release
Branch</a></li>
+</ul>
+</li>
+</ul>
+</div>
+<h1 id="checking-out-the-code">Checking out the code</h1>
+<p>You need <a href="http://subversion.tigris.org";>Subversion</a> to check out
the source code from our source code repository, and
[Maven(http://maven.apache.org/) 2.2.1 to build the source code (Building with
Maven 3.0 will also work). The following example shows how to build <a
href="http://svn.apache.org/viewvc/mina/mina/tags/2.0.7/";>the current stable
branch (2.0.7)</a>.</p>
+<div class="codehilite"><pre>$ <span class="n">svn</span> <span
class="n">co</span> <span class="n">https</span><span class="p">:</span><span
class="o">//</span><span class="n">svn</span><span class="p">.</span><span
class="n">apache</span><span class="p">.</span><span class="n">org</span><span
class="o">/</span><span class="n">repos</span><span class="o">/</span><span
class="n">asf</span><span class="o">/</span><span class="n">mina</span><span
class="o">/</span><span class="n">mina</span><span class="o">/</span><span
class="n">tags</span><span class="o">/</span>2<span class="p">.</span>0<span
class="p">.</span>7<span class="o">/</span> <span class="n">mina</span>
+$ <span class="n">cd</span> <span class="n">mina</span>
+$ <span class="n">mvn</span> <span class="o">-</span><span
class="n">Pserial</span> <span class="n">clean</span> <span
class="n">install</span> # <span class="n">Build</span> <span
class="n">packages</span> <span class="p">(</span><span
class="n">JARs</span><span class="p">)</span> <span class="k">for</span> <span
class="n">the</span> <span class="n">core</span> <span class="n">API</span>
<span class="n">and</span> <span class="n">other</span>
+ # <span class="n">extensions</span>
<span class="n">and</span> <span class="n">install</span> <span
class="n">them</span> <span class="n">to</span> <span class="n">the</span>
<span class="n">local</span> <span class="n">Maven</span> <span
class="n">repository</span><span class="p">.</span>
+$ <span class="n">mvn</span> <span class="o">-</span><span
class="n">Pserial</span> <span class="n">site</span> #
<span class="n">Generate</span> <span class="n">reports</span> <span
class="p">(</span><span class="n">JavaDoc</span> <span class="n">and</span>
<span class="n">JXR</span><span class="p">)</span>
+$ <span class="n">mvn</span> <span class="o">-</span><span
class="n">Pserial</span> <span class="n">package</span> <span
class="n">assembly</span><span class="p">:</span><span
class="n">assembly</span> # <span class="n">Generate</span> <span
class="n">a</span> <span class="n">tarball</span> <span class="p">(</span><span
class="n">package</span> <span class="n">goal</span> <span
class="n">needed</span> <span class="n">to</span> <span class="nb">fix</span>
<span class="n">an</span> <span class="n">assembly</span> <span
class="n">plugin</span> <span class="n">bug</span><span class="p">)</span>
+$ <span class="n">mvn</span> <span class="o">-</span><span
class="n">Pserial</span> <span class="n">eclipse</span><span
class="p">:</span><span class="n">eclipse</span> # <span
class="n">Generate</span> <span class="n">Eclipse</span> <span
class="n">project</span> <span class="n">files</span> <span class="k">if</span>
<span class="n">you</span> <span class="n">want</span>
+</pre></div>
-Please double-check the mode (i.e. `0664` or `-rw-rw-r--`, a.k.a permission
code) of the deployed artifacts, otherwise you can waste other people's time
significantly.
+<p>Eclipse users:
+Don't forget to declare a classpath variable named M2_REPO, pointing to
<code>~/.m2/repository</code>, otherwise many links to existing jars will be
broken.
+You can declare new variables in Eclipse in Windows -> Preferences... and
selecting Java -> Build Path -> Classpath Variables</p>
+<p>There are also other branches that might interest you:</p>
+<ul>
+<li>trunk: <a href="http://svn.apache.org/viewvc/mina/mina/trunk/";>Where big
changes take place everyday</a> -
<code>http://svn.apache.org/repos/asf/mina/mina/trunk/</code></li>
+</ul>
+<p>If you want to check out the source code of previous releases, you could
try:</p>
+<ul>
+<li><code>http://svn.apache.org/repos/asf/mina/mina/tags/</code></li>
+</ul>
+<h1 id="coding-convention">Coding Convention</h1>
+<p>We follow <a
href="http://www.oracle.com/technetwork/java/javase/documentation/codeconvtoc-136057.html";>Sun's
standard Java coding convention</a> except that we always use spaces instead
of tabs. Please download <a href="ImprovedJavaConventions.xml">the Eclipse Java
formatter settings file</a> before you make any changes to the code.</p>
+<p>This file is also available in the <code>/resources</code> directory.</p>
+<h1 id="class-header">Class header</h1>
+<p>As class header we use :</p>
+<div class="codehilite"><pre><span class="cm">/** </span>
+<span class="cm"> * Class desciption here.</span>
+<span class="cm"> *</span>
+<span class="cm"> * @author <a
href="http://mina.apache.org">Apache MINA Project</a></span>
+<span class="cm"> */</span>
+</pre></div>
-# Releasing a Point Release (Committers Only)
-## Preparing the release for the vote
+<p>The headers revisions tags are removed.</p>
+<h1 id="working-with-multiple-branches-in-one-eclipse-workspace">Working with
Multiple Branches in One Eclipse Workspace</h1>
+<p>Just running <code>mvn -Pserial eclipse:eclipse</code> won't allow you to
import MINA projects from more than one branches into one Eclipse workspace.
You have to rename all project names in the generated <code>.project</code> and
<code>.classpath</code> files to do that. Maven Eclipse plugin should provide
an option that appends the version number to the project name, but <a
href="http://jira.codehaus.org/browse/MECLIPSE-189";>this issue</a> is not being
resolved yet. Until this issue is resolved, please put the attached shell
script files ((mvnroot) and (mvn-eclipse)) to your local path (e.g.
<code>/usr/local/bin</code>) and run <code>mvn-eclipse</code>.</p>
+<div class="codehilite"><pre>$ <span class="n">svn</span> <span
class="n">co</span> <span class="n">https</span><span class="p">:</span><span
class="o">//</span><span class="n">svn</span><span class="p">.</span><span
class="n">apache</span><span class="p">.</span><span class="n">org</span><span
class="o">/</span><span class="n">repos</span><span class="o">/</span><span
class="n">asf</span><span class="o">/</span><span class="n">mina</span> <span
class="n">mina</span>
+$ <span class="n">cd</span> <span class="n">mina</span><span
class="o">/</span><span class="n">tags</span><span class="o">/</span>2<span
class="p">.</span>0<span class="p">.</span>7
+$ <span class="n">mvn</span><span class="o">-</span><span
class="n">eclipse</span>
+$ <span class="n">cd</span> <span class="p">.</span><span
class="o">./</span>2<span class="p">.</span>0<span class="p">.</span>5
+$ <span class="n">mvn</span><span class="o">-</span><span
class="n">eclipse</span>
+$ <span class="n">cd</span> <span class="p">.</span><span
class="o">./</span><span class="p">.</span><span class="o">./</span><span
class="n">trunk</span>
+$ <span class="n">mvn</span><span class="o">-</span><span
class="n">eclipse</span>
+</pre></div>
-Before starting be sure to have the java and mvn command in your PATH.
-On linux you can check with the following commands :
- $ type mvn
- mvn is hashed (/opt/maven-2.2.1/bin/mvn)
- $ type java
- java is hashed (/usr/bin/java)
+<p>Then <code>mvn eclipse:eclipse</code> command is executed internally, and
the branch name will be appended to all sub-module project files generated by
Maven Eclipse plugin.</p>
+<h1 id="deploying-snapshots-commiters-only">Deploying Snapshots (Commiters
Only)</h1>
+<p>Before running Maven to deploy artifacts, <em>please make sure if your
umask is configured correctly</em>. Unless configured properly, other
committers will experience annoying 'permission denied' errors. If your
default shell is <code>bash</code>, please update your umask setting in the
<code>~/.bashrc</code> file (create one if it doesn't exist.) by adding the
following line:</p>
+<div class="codehilite"><pre><span class="n">umask</span> 002
+</pre></div>
-### Step 0: Building MINA
-As weird as it sounds, for some unknown reason (most certainly a
misconfiguration in the Maven poms), we can't just run the release without
having previously build all the projects. This is done with the following
command :
- $ mvn clean install -Pserial
+<p>Please note that you have to edit the correct <code>shrc</code> file. If
you use <code>csh</code>, then you will have to edit <code>~/.cshrc</code>
file.</p>
+<p>Now you are ready to deploy the artifacts if you configured your umask
correctly.</p>
+<div class="codehilite"><pre>$ <span class="n">svn</span> <span
class="n">co</span> <span class="n">https</span><span class="p">:</span><span
class="o">//</span><span class="n">svn</span><span class="p">.</span><span
class="n">apache</span><span class="p">.</span><span class="n">org</span><span
class="o">/</span><span class="n">repos</span><span class="o">/</span><span
class="n">asf</span><span class="o">/</span><span class="n">mina</span><span
class="o">/</span><span class="n">tags</span><span class="o">/</span>2<span
class="p">.</span>0<span class="p">.</span>7 <span class="n">mina</span>
+$ <span class="n">cd</span> <span class="n">mina</span>
+$ <span class="n">mvn</span> <span class="o">-</span><span
class="n">Pserial</span> <span class="n">clean</span> <span
class="n">deploy</span> <span class="n">site</span> <span
class="n">site</span><span class="p">:</span><span class="n">deploy</span> #
<span class="n">Make</span> <span class="n">sure</span> <span
class="n">to</span> <span class="n">run</span> <span
class="s">'clean'</span> <span class="n">goal</span> <span
class="n">first</span> <span class="n">to</span> <span class="n">prevent</span>
<span class="n">side</span> <span class="n">effects</span> <span
class="n">from</span> <span class="n">your</span> <span
class="n">IDE</span><span class="p">.</span>
+</pre></div>
-### Step 1: Tagging and Deploying
-First you need to configure maven for using the good username for scp and
operation.
+<p>Please double-check the mode (i.e. <code>0664</code> or
<code>-rw-rw-r--</code>, a.k.a permission code) of the deployed artifacts,
otherwise you can waste other people's time significantly.</p>
+<h1 id="releasing-a-point-release-committers-only">Releasing a Point Release
(Committers Only)</h1>
+<h2 id="preparing-the-release-for-the-vote">Preparing the release for the
vote</h2>
+<p>Before starting be sure to have the java and mvn command in your PATH.
+On linux you can check with the following commands :</p>
+<div class="codehilite"><pre>$ <span class="n">type</span> <span
class="n">mvn</span>
+<span class="n">mvn</span> <span class="n">is</span> <span
class="n">hashed</span> <span class="p">(</span><span class="o">/</span><span
class="n">opt</span><span class="o">/</span><span class="n">maven</span><span
class="o">-</span>2<span class="p">.</span>2<span class="p">.</span>1<span
class="o">/</span><span class="n">bin</span><span class="o">/</span><span
class="n">mvn</span><span class="p">)</span>
+$ <span class="n">type</span> <span class="n">java</span>
+<span class="n">java</span> <span class="n">is</span> <span
class="n">hashed</span> <span class="p">(</span><span class="o">/</span><span
class="n">usr</span><span class="o">/</span><span class="n">bin</span><span
class="o">/</span><span class="n">java</span><span class="p">)</span>
+</pre></div>
-In the `~/.m2/settings.xml` you need the following lines :
- :::xml
- <settings xmlns="http://maven.apache.org/POM/4.0.0";
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
- xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
- http://maven.apache.org/xsd/settings-1.0.0.xsd";>
+<h3 id="step-0-building-mina">Step 0: Building MINA</h3>
+<p>As weird as it sounds, for some unknown reason (most certainly a
misconfiguration in the Maven poms), we can't just run the release without
having previously build all the projects. This is done with the following
command :</p>
+<div class="codehilite"><pre>$ <span class="n">mvn</span> <span
class="n">clean</span> <span class="n">install</span> <span
class="o">-</span><span class="n">Pserial</span>
+</pre></div>
- <!-- SERVER SETTINGS -->
- <servers>
- <!-- To publish a snapshot of some part of Maven -->
- <server>
- <id>apache.snapshots.https</id>
- <username>elecharny</username>
- <password>-----Your password here-----</password>
- </server>
- <!-- To publish a website of some part of Maven -->
- <server>
- <id>apache.websites</id>
- <username>elecharny</username>
- <filePermissions>664</filePermissions>
- <directoryPermissions>775</directoryPermissions>
- </server>
- <!-- To stage a release of some part of Maven -->
- <server>
- <id>apache.releases.https</id>
- <username>elecharny</username>
- <password>-----Your password here-----</password>
- </server>
- <!-- To stage a website of some part of Maven -->
- <server>
- <id>stagingSite</id> <!-- must match hard-coded repository
identifier in site:stage-deploy -->
- <username>elecharny</username>
- <filePermissions>664</filePermissions>
- <directoryPermissions>775</directoryPermissions>
- </server>
- </servers>
- <!-- PROFILE SETTINGS -->
- <profiles>
- <profile>
- <id>apache-release</id>
- <properties>
- <!-- Configuration for artifacts signature -->
- <gpg.passphrase>-----Your passphrase here-----</gpg.passphrase>
- </properties>
- </profile>
- </profiles>
+<h3 id="step-1-tagging-and-deploying">Step 1: Tagging and Deploying</h3>
+<p>First you need to configure maven for using the good username for scp and
operation.</p>
+<p>In the <code>~/.m2/settings.xml</code> you need the following lines :</p>
+<div class="codehilite"><pre><span class="nt"><settings</span> <span
class="na">xmlns=</span><span
class="s">"http://maven.apache.org/POM/4.0.0"</span>
+ <span class="na">xmlns:xsi=</span><span
class="s">"http://www.w3.org/2001/XMLSchema-instance"</span>
+ <span class="na">xsi:schemaLocation=</span><span
class="s">"http://maven.apache.org/POM/4.0.0</span>
+<span class="s">
http://maven.apache.org/xsd/settings-1.0.0.xsd"</span><span
class="nt">></span>
+
+ <span class="c"><!-- SERVER SETTINGS --></span>
+ <span class="nt"><servers></span>
+ <span class="c"><!-- To publish a snapshot of some part of Maven
--></span>
+ <span class="nt"><server></span>
+ <span class="nt"><id></span>apache.snapshots.https<span
class="nt"></id></span>
+ <span class="nt"><username></span>elecharny<span
class="nt"></username></span>
+ <span class="nt"><password></span>-----Your password
here-----<span class="nt"></password></span>
+ <span class="nt"></server></span>
+ <span class="c"><!-- To publish a website of some part of Maven
--></span>
+ <span class="nt"><server></span>
+ <span class="nt"><id></span>apache.websites<span
class="nt"></id></span>
+ <span class="nt"><username></span>elecharny<span
class="nt"></username></span>
+ <span class="nt"><filePermissions></span>664<span
class="nt"></filePermissions></span>
+ <span class="nt"><directoryPermissions></span>775<span
class="nt"></directoryPermissions></span>
+ <span class="nt"></server></span>
+ <span class="c"><!-- To stage a release of some part of Maven
--></span>
+ <span class="nt"><server></span>
+ <span class="nt"><id></span>apache.releases.https<span
class="nt"></id></span>
+ <span class="nt"><username></span>elecharny<span
class="nt"></username></span>
+ <span class="nt"><password></span>-----Your password
here-----<span class="nt"></password></span>
+ <span class="nt"></server></span>
+ <span class="c"><!-- To stage a website of some part of Maven
--></span>
+ <span class="nt"><server></span>
+ <span class="nt"><id></span>stagingSite<span
class="nt"></id></span> <span class="c"><!-- must match hard-coded
repository identifier in site:stage-deploy --></span>
+ <span class="nt"><username></span>elecharny<span
class="nt"></username></span>
+ <span class="nt"><filePermissions></span>664<span
class="nt"></filePermissions></span>
+ <span class="nt"><directoryPermissions></span>775<span
class="nt"></directoryPermissions></span>
+ <span class="nt"></server></span>
+ <span class="nt"></servers></span>
+
+ <span class="c"><!-- PROFILE SETTINGS --></span>
+ <span class="nt"><profiles></span>
+ <span class="nt"><profile></span>
+ <span class="nt"><id></span>apache-release<span
class="nt"></id></span>
+ <span class="nt"><properties></span>
+ <span class="c"><!-- Configuration for artifacts signature
--></span>
+ <span class="nt"><gpg.passphrase></span>-----Your passphrase
here-----<span class="nt"></gpg.passphrase></span>
+ <span class="nt"></properties></span>
+ <span class="nt"></profile></span>
+ <span class="nt"></profiles></span>
- </settings>
+<span class="nt"></settings></span>
+</pre></div>
-### step 2 : Processing with a dry run
-After having checked out the trunk, and built it (see step 0),
+<h3 id="step-2-processing-with-a-dry-run">step 2 : Processing with a dry
run</h3>
+<p>After having checked out the trunk, and built it (see step 0), </p>
+<div class="codehilite"><pre>$ <span class="n">svn</span> <span
class="n">co</span> <span class="n">https</span><span class="p">:</span><span
class="o">//</span><span class="n">svn</span><span class="p">.</span><span
class="n">apache</span><span class="p">.</span><span class="n">org</span><span
class="o">/</span><span class="n">repos</span><span class="o">/</span><span
class="n">asf</span><span class="o">/</span><span class="n">mina</span><span
class="o">/</span><span class="n">trunk</span> <span class="n">mina</span>
+$ <span class="n">cd</span> <span class="n">mina</span>
+$ <span class="n">mvn</span> <span class="n">clean</span> <span
class="n">install</span> <span class="o">-</span><span class="n">Pserial</span>
+</pre></div>
- $ svn co https://svn.apache.org/repos/asf/mina/trunk mina
- $ cd mina
- $ mvn clean install -Pserial
-run the following commands :
+<p>run the following commands :</p>
+<div class="codehilite"><pre>$ <span class="n">mvn</span> <span
class="o">-</span><span class="n">Pserial</span><span class="p">,</span><span
class="n">apache</span><span class="o">-</span><span class="n">release</span>
<span class="o">-</span><span class="n">DdryRun</span><span
class="p">=</span><span class="n">true</span> <span
class="n">release</span><span class="p">:</span><span class="n">prepare</span>
# <span class="n">Dry</span><span class="o">-</span><span
class="n">run</span> <span class="n">first</span><span class="p">.</span>
+</pre></div>
- $ mvn -Pserial,apache-release -DdryRun=true release:prepare # Dry-run
first.
-Answer to maven questions :
+<p>Answer to maven questions :</p>
+<div class="codehilite"><pre>"<span class="n">What</span> <span
class="n">is</span> <span class="n">the</span> <span class="n">release</span>
<span class="n">version</span> <span class="k">for</span> "<span
class="n">Apache</span> <span class="n">MINA</span>"? <span
class="p">(</span><span class="n">org</span><span class="p">.</span><span
class="n">apache</span><span class="p">.</span><span class="n">mina</span><span
class="p">:</span><span class="n">mina</span><span class="o">-</span><span
class="n">parent</span><span class="p">)</span> 2<span class="p">.</span>0<span
class="p">.</span>7<span class="o">-<</span><span
class="n">version</span><span class="o">></span><span class="p">:</span>
<span class="p">:</span>"
+<span class="o"><</span><span class="n">either</span> <span
class="n">use</span> <span class="n">the</span> <span class="n">default</span>
<span class="n">version</span> <span class="n">as</span> <span
class="n">suggested</span><span class="p">,</span> <span class="n">or</span>
<span class="n">type</span> <span class="n">in</span> <span
class="n">the</span> <span class="n">version</span> <span
class="n">you</span><span class="p">@</span><span class="n">qot</span><span
class="p">;</span><span class="n">d</span> <span class="n">like</span> <span
class="n">to</span> <span class="n">be</span> <span class="n">used</span><span
class="o">></span>
+<span class="p">[..]</span>
+</pre></div>
- "What is the release version for "Apache MINA"?
(org.apache.mina:mina-parent) 2.0.7-<version>: :"
- <either use the default version as suggested, or type in the version
you@qot;d like to be used>
- [..]
<DIV class="info" markdown="1">
Just after the last module, maven will ask you about the SCM tag :
Modified: websites/staging/mina/trunk/content/mina-project/documentation.html
==============================================================================
--- websites/staging/mina/trunk/content/mina-project/documentation.html
(original)
+++ websites/staging/mina/trunk/content/mina-project/documentation.html Sat Nov
2 06:23:18 2013
@@ -136,14 +136,14 @@
-<H1>Documentation</H1>
-
+<h1 id="documentation">Documentation</h1>
<DIV class="note" markdown="1">
The MINA 2.0 User Guide can be found here : [User
Guide](userguide/user-guide-toc.html)
</DIV>
<div class="toc">
<ul>
+<li><a href="#documentation">Documentation</a><ul>
<li><a href="#presentation-materials">Presentation Materials</a></li>
<li><a href="#versions-references">Versions & References</a></li>
<li><a href="#tutorials">Tutorials</a><ul>
@@ -153,6 +153,8 @@ The MINA 2.0 User Guide can be found her
<li><a href="#examples">Examples</a></li>
<li><a href="#older-presentation-materials">Older Presentation
Materials</a></li>
</ul>
+</li>
+</ul>
</div>
<h2 id="presentation-materials">Presentation Materials</h2>
<p>These presentation materials will help you understand the overall
architecture and core constructs of MINA</p>
