HowToSubmitPatches

UserPreferences

This wiki is in 'slumber' mode, just like its associated sourceforge project. Edits are disabled, the content is potentially stale and is not maintained. That said, it contains some really useful stuff still. Enjoy!

Submitting a bugreport

Jicarilla does not use an issue tracker (at the moment). Instead, you should send bug reports to the mailing list. To do so, please follow the following conventions. Doing so will make bug and patch management possible for the project developers. If you don't, your messages may get lost.

Subject prefix

[patch]

If you're providing a code modifications. Please submit all patches as attachments. Use unified diffs (see below). Please provide unit tests with all patches (unless the unit test for your patch already exists).

[rfe]

If you're submitting or requesting an improvement over existing code or new functionality, rather than reporting a 'real' bug.

[bug]

If you're reporting a real bug or submitting a patch to fix one.

Please remove the [patch] from the subject line when replying to a patch submission (keep the other prefixes as long as they're appropriate). Examples:

[patch][bug] UnsatisfiableDependencyException does not check for null

[rfe] Spring framework support

Re: [rfe] Spring framework support

[patch][rfe] Spring framework support

Re: [bug] UnsatisfiableDependencyException does not check for null

[bug] CyclicDependecyException when loading my merlin-based components

Debugging information

More debug info is generally better than less.

• If a testcase failed, please attach the failure log.
• If a build failed, please attach the build log.
• Always describe what led to the problem precisely.
• Please mention (exactly) what version of the various software components you're using.
• Include environmental information (OS, java environment, environment settings, locations and versions of used tools, etc).
• If an error occured, please attach the stack trace and all error messages.
• Please use the debug mode when possible.

Submitting patches

• Please send patches as attachments with a .patch.txt suffix, or as zipfiles when they're big.
• Submit patches as unified diffs.
• Generate diffs relative to the cvs module root.
• Please follow code conventions, include full javadoc, and full unit tests with all patches.

See http://www.apache.org/dev/contributors.html#patches for a more verbose guide to patch submisson.

The contents of this wiki are licensed under a Creative Commons License.