Re: svn commit: r1660469 - /mina/site/trunk/content/mina-project/developper-guide.mdtext

[sebb <se...@gmail.com>]

On 17 February 2015 at 19:24,  <el...@apache.org> wrote:
> Author: elecharny
> Date: Tue Feb 17 19:24:05 2015
> New Revision: 1660469
>
> URL: http://svn.apache.org/r1660469
> Log:
> Removed references to SVN
>
> Modified:
>     mina/site/trunk/content/mina-project/developper-guide.mdtext

Might wish to consider renaming this file - developper looks rather oddd (!) ...

>
> Modified: mina/site/trunk/content/mina-project/developper-guide.mdtext
> URL: http://svn.apache.org/viewvc/mina/site/trunk/content/mina-project/developper-guide.mdtext?rev=1660469&r1=1660468&r2=1660469&view=diff
> ==============================================================================
> --- mina/site/trunk/content/mina-project/developper-guide.mdtext (original)
> +++ mina/site/trunk/content/mina-project/developper-guide.mdtext Tue Feb 17 19:24:05 2015
> @@ -26,7 +26,7 @@ Notice:    Licensed to the Apache Softwa
>
>  # Checking out the code
>
> -You need Git 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/).
> +You need Git 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.9).
>
>      $ git clone http://git-wip-us.apache.org/repos/asf/mina.git mina
>      $ cd mina
> @@ -72,24 +72,6 @@ As class header we use :
>
>  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.
> -
> -<DIV class="note" markdown="1">
> -Working with Eclipse LUNA allows you to import the pom.xml directly into the workspace, instead of running mvn eclipse:eclipse, which is quite convenient. Although you still need to tweak your pom if you want to work with more than one version of MINA in your workspace.
> -</DIV>
> -
>  # 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:
> @@ -100,7 +82,7 @@ Please note that you have to edit the co
>
>  Now you are ready to deploy the artifacts if you configured your umask correctly.
>
> -    $ svn co https://svn.apache.org/repos/asf/mina/tags/2.0.7 mina
> +    $ git clone http://git-wip-us.apache.org/repos/asf/mina.git mina
>      $ cd mina
>      $ mvn -Pserial clean deploy site site:deploy    # Make sure to run 'clean' goal first to prevent side effects from your IDE.
>
> @@ -183,7 +165,7 @@ In the `~/.m2/settings.xml` you need the
>
>  After having checked out the trunk, and built it (see step 0),
>
> -    $ svn co https://svn.apache.org/repos/asf/mina/trunk mina
> +    $ git clone http://git-wip-us.apache.org/repos/asf/mina.git mina
>      $ cd mina
>      $ mvn clean install -Pserial
>
> @@ -455,9 +437,7 @@ Here is how you  send a [VOTE] mail on t
>
>      https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10670&styleName=Html&version=12313702
>
> -    A temporary tag has been created (it can be removed if the vote is not approved):
> -    http://svn.apache.org/viewvc/mina/tags/2.0.1/
> -    The svn revision is :http://svn.apache.org/viewvc?rev=1026395
> +    A temporary tag has been created (it can be removed if the vote is not approved)
>
>      The newly approved Nexus has been used for the preparation of this release and all final artifacts are stored
>      in a staging repository:
> @@ -564,26 +544,3 @@ We need to wait until any changes made i
>
>  An announcement message can be sent to [mailto:announce@apache.org], [mailto:announce@apachenews.org], [mailto:users@mina.apache.org] and [mailto:dev@mina.apache.org].  Please note that announcement messages are rejected unless your from-address ends with `@apache.org`.  Plus, you shouldn't forget to post a news to the MINA site main page.
>
> -## Creating a New Release Branch
> -
> -When you create a new branch, you have to make sure the sections that specifies branch version numbers are configured appropriately in the root `pom.xml`.
> -
> -       :::xml
> -    ...
> -    <version>1.1.0-SNAPSHOT</version>
> -    ...
> -    <scm>
> -      <connection>scm:svn:http://svn.apache.org/repos/asf/mina/mina/branches/2.0</connection>
> -      <url>http://svn.apache.org/viewvc/directory/mina/mina/branches/2.0</url>
> -      <developerConnection>scm:svn:https://svn.apache.org/repos/asf/mina/mina/branches/2.0</developerConnection>
> -    </scm>
> -    ...
> -    <distributionManagement>
> -      <site>
> -        <id>apache.websites</id>
> -        <url>scp://people.apache.org/www/mina.apache.org/report/1.1/</url>
> -      </site>
> -    </distributionManagement>
> -    ...
> -
> -Please note that the example above is for `branches/2.0`.  For example, you have to replace `branches/2.0` with `branches/3.0` if the version number of the new branch is 3.0.  In case of `trunk`, it's just `trunk` rather than `branches/<version>`.
>
>