| | 1 | = Using Maven Build Tools = |
| | 2 | |
| | 3 | [[TracNav]] |
| | 4 | [[TOC(inline)]] |
| | 5 | |
| | 6 | Maven is a Java-based system that provides a standard file format for build information, well-defined build lifecycle, and plugin framework for extensions. There also exist standard repositories in which both development and production packages (artifacts) can be maintained. The maven plugins are also available through standard maven repositories, allowing the core maven code to be very small. Any real build, however, will require a large number of additional plug-ins that are downloaded automatically and cached on the user's machine. |
| | 7 | |
| | 8 | == Installing Maven == |
| | 9 | |
| | 10 | To download and install maven see the [http://maven.apache.org/ maven website]. Essentially the only required dependency is a recent, certified version of a Java Virtual Machine. This installation provides a command line interface to maven, the primary command being `mvn`. |
| | 11 | |
| | 12 | Maven also integrates well with Eclipse. The [http://m2eclipse.sonatype.org/ m2eclipse plugin] is recommended. |
| | 13 | |
| | 14 | == Running Maven == |
| | 15 | |
| | 16 | Running maven should be as simple as checking out the Quattor code and then running `mvn package`. This will prepare the sources, compile them (if necessary), and package the results. If on a machine which supports RPM packaging, RPM packages will be produced. In all cases, appropriate tarballs will be generated. |
| | 17 | |
| | 18 | |
