Bureaucrats, editor, reviewer, Administrators
13,550
edits
Changes
Jump to navigation
Jump to search
To launch the core project, There are several alternatives for starting BaseX: * type in <code>{{Code|java -cp target/classes org.basex.BaseX</code>}} in the {{Code|basex-core}} directory to start BaseX on the command-line mode,* type in {{Code|mvn jetty:run}} in the {{Code|basex-api}} directory to start BaseX with Jetty and the HTTP servers, or have a look at * run one of the [[Start Scripts]] contained in the {{Code|etc}} directory.
[[Category:Developer]]
no edit summary
==Using Maven==
If you have [[Git|cloned our repositoriesrepository]] and installed Maven on your machine,
you can run the following commands from all local repository directories:
* <code>mvn compile</code>: the BaseX source files are compiled.
* <code>mvn package</code>: JAR archives are created in the {{Code|target}} class directory, and all relevant libraries are created in the {{Code|lib}} directory. Packaging is useful if you want to use the [[Start Scripts]]start scripts.
* <code>mvn install</code>: 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 <code>-DskipTests</code> you can skip the JUnit tests and speed up packaging. You may as well use [[Developing with Eclipse|Eclipse and m2eclipse]] to compile the BaseX sources.
==Artifacts==
<groupId>org.basex</groupId>
<artifactId>basex</artifactId>
<version>7.56</version>
</dependency></pre>
<groupId>org.basex</groupId>
<artifactId>basex-api</artifactId>
<version>7.56</version>
</dependency></pre>
</dependency>
</pre>
