|
Size: 1120
Comment:
|
← Revision 3 as of 2010-03-17 13:09:16 ⇥
Size: 1117
Comment: converted to 1.6 markup
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 3: | Line 3: |
| This page describes the structure a module releases must follow. It also specifies how the [:Ant: Ant] {{{release.*}}} targets work. | This page describes the structure a module releases must follow. It also specifies how the [[Ant]] {{{release.*}}} targets work. |
| Line 12: | Line 12: |
| These files ''must'' extract into a {{{doms-<module>-<version>}}} directory. The internal structure should follow that of the [:Directory_layout: module directory guidelines]. | These files ''must'' extract into a {{{doms-<module>-<version>}}} directory. The internal structure should follow that of the [[Directory layout| module directory guidelines]]. |
Project Release Structure
This page describes the structure a module releases must follow. It also specifies how the 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 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.