Differences between revisions 1 and 2
Revision 1 as of 2008-06-26 12:26:09
Size: 1116
Editor: kfc
Comment: Created by the PackagePages action.
Revision 2 as of 2009-08-24 14:17:58
Size: 1120
Editor: jrg
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
= Module Release Structure = = Project Release Structure =
Line 8: Line 8:
 * doms-<module>-<version>.zip (binary release)
 * doms-<module>-<version>-src.zip (source release)
 * doms-<module>-<version>-apidocs.zip (apidocs release)
 * doms-<project>-<version>.zip (binary release)
 * doms-<project>-<version>-src.zip (source release)
 * doms-<project>-<version>-apidocs.zip (apidocs release)

Project Release Structure

This page describes the structure a module releases must follow. It also specifies how the [:Ant: Ant] release.* targets work.

Release Files

A release consists of three zip files

  • doms-<project>-<version>.zip (binary release)

  • doms-<project>-<version>-src.zip (source release)

  • doms-<project>-<version>-apidocs.zip (apidocs release)

These files must extract into a doms-<module>-<version> directory. The internal structure should follow that of the [:Directory_layout: module directory guidelines].

Binary Releases

Contains compiled code packaged into neat .jar files with all dependencies included.

Source Releases

A source release contains all source code and build files needed to compile a release. A source release must be able to "bootstrap" in the sense that it should be able to compile binary-, source-, and apidocs releases as described in this document.

Apidocs Releases

Contains only the contents of the apidocs directory. Other documentation should go with the source release.

ModuleReleaseStructure (last edited 2010-03-17 13:09:16 by localhost)