Difference between revisions of "Maven"
Jump to navigation
Jump to search
Line 12: | Line 12: | ||
By adding the flag <code>-DskipTests</code> you can skip the JUnit tests and speed up packaging. You may as well use [[Eclipse|Eclipse and m2eclipse]] to compile the BaseX sources. | By adding the flag <code>-DskipTests</code> you can skip the JUnit tests and speed up packaging. You may as well use [[Eclipse|Eclipse and m2eclipse]] to compile the BaseX sources. | ||
− | + | There are several alternatives for starting BaseX: | |
+ | |||
+ | * type in {{Code|java -cp target/classes org.basex.BaseX}} in the {{Code|basex}} repository to start the command-line mode, | ||
+ | * type in {{Code|mvn jetty:run}} in the {{Code|basex-api}} repository to start BaseX with Jetty and the HTTP servers, | ||
+ | * run one of the [[Start Scripts]] contained in the {{Code|etc}} directory | ||
==Artifacts== | ==Artifacts== |
Revision as of 12:58, 30 January 2013
This page is part of the Developer Section. It demonstrates how Maven is used to compile and run BaseX, and embed it into other projects.
Using Maven
If you have cloned our repositories and installed Maven on your machine, you can run the following commands from all local repository directories:
mvn compile
: the BaseX source files are compiled.mvn package
: JAR archives are created in thetarget
class directory, and all relevant libraries are created in thelib
directory. Packaging is useful if you want to use the start scripts.mvn install
: the JAR archive is installed to the local repository, and made available to other Maven projects. This is particularly useful if you are compiling a beta version of BaseX, for which no archives exist in the repositories.
By adding the flag -DskipTests
you can skip the JUnit tests and speed up packaging. You may as well use Eclipse and m2eclipse to compile the BaseX sources.
There are several alternatives for starting BaseX:
- type in
java -cp target/classes org.basex.BaseX
in thebasex
repository to start the command-line mode, - type in
mvn jetty:run
in thebasex-api
repository to start BaseX with Jetty and the HTTP servers, - run one of the Start Scripts contained in the
etc
directory
Artifacts
You can easily embed BaseX into your own Maven projects by adding the following XML snippets to your pom.xml
file:
<repositories> <repository> <id>basex</id> <name>BaseX Maven Repository</name> <url>http://files.basex.org/maven</url> </repository> </repositories>
BaseX Main Package
<dependency> <groupId>org.basex</groupId> <artifactId>basex</artifactId> <version>7.5</version> </dependency>
APIs and Services
...including APIs and the REST, RESTXQ and WebDAV services:
<dependency> <groupId>org.basex</groupId> <artifactId>basex-api</artifactId> <version>7.5</version> </dependency>
XQJ API
The XQJ API is hosted at http://xqj.net:
<repository> <id>xqj</id> <name>XQJ Maven Repository</name> <url>http://xqj.net/maven</url> </repository> ... <dependency> <groupId>net.xqj</groupId> <artifactId>basex-xqj</artifactId> <version>1.2.0</version> </dependency> <dependency> <groupId>com.xqj2</groupId> <artifactId>xqj2</artifactId> <version>0.1.0</version> </dependency> <dependency> <groupId>javax.xml.xquery</groupId> <artifactId>xqj-api</artifactId> <version>1.0</version> </dependency>