ATM only build logs are published as a result of a build. This is far from enough, and a decent CI server requires numerous build result publication.

The idea in xooctory is to make this result publication very flexible, and extensible.

The aim of this issue is to provide the architecture for publication, to allow easy and flexible plugin development. Other issues will be created to address the plugin themselves (Junit, Compilation, Javadoc, ...).

ATM the foreseen architecture will define a way to add a publication plugin, and to define which publication plugin to use for which job plan.

It will also define publication objects (what is published by the build) with easy definition of the attributes of this objects, including file attributes.

The framework will allow to assign a durability to a publication object: should the object be kept only until the next build, or for 10 builds, or 5 succesfull builds, or one year, or forever, ...

The framework will also define a pretty frequent publication object: file annotation. A file annotation is very close to the concept of marker in eclipse (maybe using eclipse terminology would be better?)..
It is defined by:

• a type (junit, compilation, checkstyle, ...)
• the file to which it is attached,
• the line and optionally the column,
• a severity (error, warning, info, ...)
• a detailed text

This concept can be used to address many different kind of publications, such as junit, checkstyle, findbugs, compilation, ...