Taglets Collection

Java-based build tool similar to the Unix make tool.

A collection of tasks and utilities for Apache Ant.

Custom MuliFex Ant Tool Tasks.

Currently the following tasks are included:

toollist

Helper task for the tooldoc project tool.

xsltdoc

Extended xslt task that automatically passes in some parameters (like generation source, timestamp, etc.). This task is mainly to prevent cluttered build files that have the same copy/pasted lines all over the place.

webdoc

Documentation build task that builds webpages for the tigris-style. It takes a couple of HTML files as well as a site description file as input and creates the whole webpage including navigation, breadcrumbs, etc. pp. Take a look at build.xml on how it is used for MuliFex.

dom4j is an Open Source XML framework for Java.

dom4j allows you to read, write, navigate, create and modify XML documents. It integrates with DOM and SAX and is seamlessly integrated with full XPath support.

This tool provides a wrapper for the tools.jar shipped with the JDK.

According to the build settings in your env/site.xml or env/user.xml this wrapper copies the tools.jars of your J2SE 1.4 and J2SE 1.5 installation as well as its sources to the project environment.

Lightbox is a simple, unobtrusive script used to overlay images on the current page. It's a snap to setup and works on all modern browsers.

Fantastic tool and works perfect in combination with MurImages.

Photo Collage II aka Mur d'Images, collage and image map generator by Hervé Perez.

This is an enhanced version of Romain Guy's Photo Collage .

Includes a modified version of the High Performance JavaScript Vector Graphics Library by Walter Zorn.

The version included is a modified WebStart version that allows local execution using java -jar murimages.jar.

Prettify is embedded in JavaDoc generated to pretty print code tags such as {@source} or {@example}.

Google Code Prettify

Some functions for browser-side pretty printing of code contained in html.

The lexer should work on a number of languages including C and friends, Java, Python, Bash, SQL, HTML, XML, CSS, Javascript, and Makefiles. It works passably on Ruby, PHP and Awk and a decent subset of Perl, but, because of commenting conventions, doesn't work on Smalltalk, Lisp-like, or CAML-like languages.

If there's a language not mentioned here, then I don't know it, and don't know whether it works. If it has a C-like, Bash-like, or XML-like syntax then it should work passably.

Usage:

1. Include this source file in an html page via <script type="text/javascript" src="/path/to/prettify.js"></script>
2. Add onload="prettyPrint();" to the document body tag.
3. Define style rules. See the example page for examples.
4. Mark the <pre> and <code> tags in your source with class=prettyprint.

Cascading stylesheets for web applications.

The project webpage as well as the user guide and the developer documentation make use of the tigris style.

This "build tool" therefore consists of resources used unmodified as well as some driver scripts to generate the documentation.

Customizations to the tigris style are stored in the documentation resource folder of the project.

Ant task and XSLT documentation drivers for tool descriptions.

Each tool used resides in its own folder and is described by a simple XML file (take a look at some of the tool.xml files in the /tool/<toolgroup>/<toolname> subfolders.

Groups of tools (such as build tools, libraries, etc.) are also grouped in a folder and there is an overview description file called tools.xml which describes the tool group. Take a look e.g. at /tool/build/tools.xml.

Generation of tool information webpages is a two-step process:

1. Generation of a unified tool information XML file using the toollist ant task (have a look at the ant driver file /tool/build/toodoc/ant.xml on how to invoke toollist).
2. Generation of the a single webpage for each tool group using the tooldoc style sheets (used in build.xml to build pages like the one you're currently viewing).

There is not much documentation about tooldoc but most of what's here should be self-explanatory -- and of course there's also the source :-).