- The Torque build process uses - Maven 1. The recommended - Maven version is Maven 1.0.2. A rudimentary - Maven 2 build exists (see below), - but is only used to build the Maven 2 plugin. -
- Note that the Maven 1 build uses the groupId torque, - wheras the Maven 2 build uses the group id - org.apache.db.torque. -

- Before you begin, you'll need to check out the trunks + The Torque build process uses + Maven 2. + You need ton install Maven 2 in order to be able to build torque. + Then, you need to check out the torque4/trunk part of the db/torque SVN repository. Please read the Torque Subversion page for more information.

- -

- To build the Torque generator jar, first execute - maven jar:install in the - templates directory to install a copy - of the templates jar in your local Maven repository. Note that - maven jar:jar does not suffice because the - main generator jar depends upon the template jar. - Afterwards, execute maven jar:jar in the generator - directory to build the generator jar (maven jar:install - to install a copy of the jar in your local Maven repository). -

- To build and install the Torque Maven 1 plugin, execute maven - plugin:install in the maven-plugin directory. - You need to have the generator installed in your local repository - to do that (see paragraph above). -

- To build the Torque runtime jar execute maven jar:jar in - the runtime directory - (maven jar:install to install a copy of the jar - in your local Maven repository). -

- If you need everything at once, run maven install in the - top level directory. This will perform all the steps described above and - place the results into your local maven repository. -

- The Torque Maven 2 plugin cannot be built using Maven 1. + Change into the directory torque-maven-parent in your local copy + of the torque 4 trunk. Run "mvn install". The runtime, generator, + templates and maven 2 plugin will be built in turn and installed + in your local maven 2 repository.

- -

- Change into the directories common, village, runtime, templates, generator, and - maven2-plugin in this order and run mvn install - in each of them. -

- The Torque Maven 1 plugin cannot be built using Maven 2. + Change into the directory torque-maven-parent in your local copy + of the torque 4 trunk. Run + "mvn eclipse:configure-workspace install eclipse:clean eclipse:eclipse". + Then start eclipse, and open the directoy you checked out from svn + as eclipse workspace. Create the projects "torque-runtime", + "torque-maven-parent", "maven-torque-plugin", "torque-generator" + and "torque-templates" (the contents of the projects are already + in the workspace). That's it.

- Up to release 3.1.1, Torque used CVS as its source code - repository. Most of the older releases still point to the CVS - repository at cvs.apache.org. During the 3.2 development cycle, - the Torque team (with a few well-meant nudges from the Apache - Software Foundation infrastructure team) decided to move the - Torque source code from CVS to Subversion. -

- -

+ The Torque source code is located inside the Apache Software + Foundation's + subversion + repository. If you have never worked with Subversion before, please take a look at the free subversion book and also at

- Unlike some other repositories you might know, Torque makes some - use of the svn:externals - feature of Subversion to organize its tree. This might lead to - some "gotchas", so be warned. -

- +

- Here is what the Torque directory structure looks like in SVN: + The base directory of torque 4 is db/torque/torque4. + The main branch is located in the trunk subdirectory of that + directory. The layout is:

@@ -89,19 +73,19 @@ - - - - - - - - + + + + + + + +

Component	Trunk repository location
Runtime	http://svn.apache.org/repos/asf/db/torque/runtime/trunk
Generator	http://svn.apache.org/repos/asf/db/torque/generator/trunk/
Templates	http://svn.apache.org/repos/asf/db/torque/templates/trunk/
Maven 1 Plugin	http://svn.apache.org/repos/asf/db/torque/maven-plugin/trunk/
Maven 2 Plugin	http://svn.apache.org/repos/asf/db/torque/maven2-plugin/trunk/
Site	http://svn.apache.org/repos/asf/db/torque/site/trunk/
Common	http://svn.apache.org/repos/asf/db/torque/common/trunk/
Test	http://svn.apache.org/repos/asf/db/torque/test/trunk/
Runtime	http://svn.apache.org/db/torque/torque4/trunk/torque-runtime
Generator	http://svn.apache.org/db/torque/torque4/trunk/torque-generator
Templates	http://svn.apache.org/repos/asf/db/torque/torque4/trunk/torque-templates
Maven 2 Plugin	http://svn.apache.org/repos/asf/db/torque/torque4/trunk/torque-maven-plugin
Site	http://svn.apache.org/repos/asf/db/torque/torque4/trunk/site/
Tutorial	http://svn.apache.org/repos/asf/db/torque/torque4/trunk/tutorial
Maven parent	http://svn.apache.org/repos/asf/db/torque/torque4/trunk/torque-maven-parent
Test	http://svn.apache.org/repos/asf/db/torque/torque4/trunk/test

- +

These modules make up the main torque distribution. They are released in regular intervals and are available as binary @@ -113,16 +97,10 @@

- +

- The common module is a special module because it contains files - that are needed in all main modules of the Torque source - tree. Every module pulls it into its source tree through an - external reference and references the files in the common module - as /common/...
- Please be aware that every change - inside this module influences the build process of all the - Torque modules!. + The maven parent module is a special module because it contains files + that are needed in all main modules of the Torque source tree.

@@ -142,63 +120,68 @@

- All CVS tags and branches that existed before the conversion to Subversion have - been preserved. These are only for historic reasons and there will be no more - development here. Branches and Tags after the Subversion conversion will be located - in the module specific branches/ and tags/ directories. - -

- Old CVS Tags - -- http://svn.apache.org/repos/asf/db/torque/tags/ -
- Old CVS Branches - -- http://svn.apache.org/repos/asf/db/torque/branches/ -

+ + +

+ Here are the torque 3 paths in SVN: +

+ + + + + +

+ The Torque subversion repository contains another module for + development called trunks. While + this module seems quite empty, it is not.
+ If you want to work on the Torque code base, your best guess will be to + check out this module using + + + + The resulting directory will contain the trunk locations of all + main Torque parts. This also happens through svn:external + references.

+ -

- The Torque subversion repository contains another module for - development called trunks. While - this module seems quite empty, it is not.
- If you want to work on the Torque code base, your best guess will be to - check out this module using - - - - The resulting directory will contain the trunk locations of all - main Torque parts. This also happens through svn:external - references. -

+ +

+ All CVS tags and branches that existed before the conversion to Subversion have + been preserved. These are only for historic reasons and there will be no more + development here. Branches and Tags after the Subversion conversion will be located + in the module specific branches/ and tags/ directories. + +

+ Old CVS Tags + -- http://svn.apache.org/repos/asf/db/torque/tags/ +
+ Old CVS Branches + -- http://svn.apache.org/repos/asf/db/torque/branches/ +

- The trunks module also contains a Multi-Project - build environment to build all the major parts of Torque in one - go.
- If you checked out the trunks module from subversion, you can run one of - the following goals inside the resulting directory: - -

- build -- Builds all parts of Torque -
- install - Builds all parts of Torque and installs the resulting jars - and plugins into your local maven repository -
- site -- Builds the documentation sites for all parts of Torque -

--------------------------------------------------------------------- To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org For additional commands, e-mail: torque-dev-help@db.apache.org