Avalon uses the ASF JIRA issue tracker to manage feature requests and bug fixes. Anyone can browse project reports, though you will need an account to submit new issues. Please submit requests to the appropriate project module (when in doubt, send a message to the developers mailing list).
| Project | Description |
|---|---|
| Avalon Central | Site docs, General Issues |
| Avalon Planet | Components and facilities. |
| Avalon Tools | Avalon's build system and general developer tools. |
| Merlin Runtime | Avalon Merlin RI Container. |
| Merlin Studio | Exclipse support tools for Merlin component development. |
A full list of the projects can be found at http://issues.apache.org/jira in the Avalon, Avalon Merlin, and Avalon Components categories.
Generate patches using cvs diff -u, or diff -u.
Please create your patches relative to the root of the cvs module the patch
should be applied to. Please compile changes to multiple files
in a single patch file. Make sure the patch adheres to the coding standards,
and includes appropriate javadoc.
When you've built the patch, file a new bug report in JIRA if one does not exist yet, explain the reason behind the patch, how the patch fixes the issues, and add the patch as an attachment.
If your patch is not getting applied or there is no response, start nagging the developers (politely, please :D) on the developers mailing list.
Please submit documentation patches against the XML sourcefiles used for generating the documentation, and not against the documentation itself. Site documentation issues can be opened in the Avalon Framework's Documentation module.
