Overview

• Introduction
• Features
• Goals
• Usage
• Configuration

Examples

• Simple Example
• Complex Example

Project Documentation

• Project Information
  • Dependencies
  • Dependency Information
  • Distribution Management
  • About
  • Licenses
  • Plugin Management
  • Plugins
  • Source Code Management
  • Summary
  • Team
• Project Reports

This site is under construction. Thus we refer the reader to the development site and in particularly the the 'README.md' therein. Check in particular the section on the maven plugin. For a really detailled description in contrast see manual. Note that this manual is created by this maven-latex-plugin and serves also as a testsuite for the plugin. This is also why it is available as pdf only: the html output is not mature and comprehensive enough to compile the manual.

If you have problems applying it or feel a feature is missing, please dont hesitate and let me know.

The maven-latex-plugin translates LaTeX documents into PDF, HTML or other LaTeX output formats like DVI or Postscript, during the maven site lifecycle. Internally, the plugin calls the standard LaTeX macros, like pdflatex for PDF and tex4ht for HTML output. Hence, a LaTeX distribution has to be installed on the computer running the maven build.

By default, LaTeX documents and resources like graphics files are assumed to reside in the maven project's src/site/tex folder. The resulting files will be in the folder target/site/tex, making them a part of the maven site. Thus, other maven site artifacts (like HTML pages build from apt files) may link to them.

The maven-latex-plugin tries to be smart by analyzing the LaTeX macros' output and running the macros as often as needed (running LaTeX more than once is needed when e.g. building a table of contents or when using bibtex to maintain a bibliography and citations).