You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@velocity.apache.org by cb...@apache.org on 2017/11/13 11:47:43 UTC
svn commit: r1815087 - in /velocity/site/cms/trunk/content/engine:
2.0/build.mdtext devel/build.mdtext
Author: cbrisson
Date: Mon Nov 13 11:47:42 2017
New Revision: 1815087
URL: http://svn.apache.org/viewvc?rev=1815087&view=rev
Log:
[site] Review build instructions
Modified:
velocity/site/cms/trunk/content/engine/2.0/build.mdtext
velocity/site/cms/trunk/content/engine/devel/build.mdtext
Modified: velocity/site/cms/trunk/content/engine/2.0/build.mdtext
URL: http://svn.apache.org/viewvc/velocity/site/cms/trunk/content/engine/2.0/build.mdtext?rev=1815087&r1=1815086&r2=1815087&view=diff
==============================================================================
--- velocity/site/cms/trunk/content/engine/2.0/build.mdtext (original)
+++ velocity/site/cms/trunk/content/engine/2.0/build.mdtext Mon Nov 13 11:47:42 2017
@@ -14,13 +14,13 @@ To build Velocity we require [Maven](htt
## Building
-In each case below, it is assumed that you were successful in getting the distribution from Subversion, and were successful in unpacking. Also, it is assumed that you are starting in the 'velocity' directory, the root of the distribution tree. All directory references will be relative to 'velocity'.
-
-Change to the **build** directory (`cd build`). Then, to build the jar file, simply type:
+In each case below, it is assumed that you were successful in [downloading](/download.cgi#engine) and unpacking the distribution source or [checking out the sources from Subversion](/download.cgi#source-code-repository):
+ svn checkout https://svn.apache.org/repos/asf/velocity/engine/tags/2.0 velocity-2.0
+ cd velocity-2.0
mvn install
-Executing this script will create a **target** directory within the Velocity distribution directory. Each subdirectory containing a module of Velocity will contain a "target" directory too, containing all built jars. In the "velocity-assembly" module you will find built distributions.
+Executing this script will create a **target** directory within the velocity-2.0 directory. Each subdirectory containing a module of Velocity will contain a "target" directory too, containing all built jars.
Refer to Maven documentation for all phases you can invoke.
Modified: velocity/site/cms/trunk/content/engine/devel/build.mdtext
URL: http://svn.apache.org/viewvc/velocity/site/cms/trunk/content/engine/devel/build.mdtext?rev=1815087&r1=1815086&r2=1815087&view=diff
==============================================================================
--- velocity/site/cms/trunk/content/engine/devel/build.mdtext (original)
+++ velocity/site/cms/trunk/content/engine/devel/build.mdtext Mon Nov 13 11:47:42 2017
@@ -12,15 +12,15 @@ Everything required to build Velocity co
To build Velocity we require [Maven](http://maven.apache.org/) version 3.0.5 or higher to perform the build process. We assume that you have followed Maven's installation instructions and have it properly installed.
-## Building
+## Building from Sources
-In each case below, it is assumed that you were successful in getting the distribution from Subversion, and were successful in unpacking. Also, it is assumed that you are starting in the 'velocity' directory, the root of the distribution tree. All directory references will be relative to 'velocity'.
+In each case below, it is assumed that you were successful in [checking out the sources from Subversion](/download.cgi#source-code-repository):
-Change to the **build** directory (`cd build`). Then, to build the jar file, simply type:
+ svn checkout https://svn.apache.org/repos/asf/velocity/engine/trunk velocity
+ cd velocity
+ mvn install
- mvn install
-
-Executing this script will create a **target** directory within the Velocity distribution directory. Each subdirectory containing a module of Velocity will contain a "target" directory too, containing all built jars. In the "velocity-assembly" module you will find built distributions.
+Executing this script will create a **target** directory within the velocity directory. Each subdirectory containing a module of Velocity will contain a "target" directory too, containing all built jars.
Refer to Maven documentation for all phases you can invoke.