accumulo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Medinets (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-704) Change the target maven lifecycle for user manual pdf creation
Date Thu, 02 Aug 2012 23:19:03 GMT


David Medinets commented on ACCUMULO-704:
The reason is as follows:

    At the first latex run, all \cite{...} arguments are written in the file document.aux.

    At the bibtex run, this information is taken by bibtex and the relevant entries are put
into the .bbl file.

    At the next run of latex, the .bbl file is included and correct labels for \cite{...}
commands are written in .aux file

    Only at the last run, latex knows what the correct labels are and includes them in the

The reason why TeX and BibTeX have been made this way is that back then, the memories used
to be small, and file systems were the only good ways to store files. But you cannot read
and write the same file (well, you can, but it's more complicated), that's why you have to
run latex twice after bibtex, as well as you have to run it twice where you cross-reference
> Change the target maven lifecycle for user manual pdf creation
> --------------------------------------------------------------
>                 Key: ACCUMULO-704
>                 URL:
>             Project: Accumulo
>          Issue Type: Task
>          Components: docs
>    Affects Versions: 1.5.0
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>            Priority: Trivial
>             Fix For: 1.5.0
> The script to create the user manual pdf is run as a part of the prepare-package lifecycle,
which means that any user running `package` or `install` will be forced to have latex installed
with the necessary dependencies to build the user manual (see ACCUMULO-702).
> Remove the user-manual creation from prepare-package and place it somewhere more suitable.
Perhaps `site` would make sense, perhaps a special profile would do the trick too.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message