axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Glyn Normington" <glyn_norming...@uk.ibm.com>
Subject RE: Beta Fix candidate on Call.java
Date Tue, 19 Mar 2002 09:42:10 GMT

Vaidya,

You wrote:
>I want to contribute to the development of the Axis as a developer.
>Could you guys tell me how do I go about this?

Great!

Try reading http://xml.apache.org/axis/overview.html and
http://jakarta.apache.org/site/getinvolved.html for some clues.

It's not hard to find ways to improve Axis, so I'd suggest getting it
running (and send patches for documentation problems you notice as these
will benefit many people) and then coding some simple improvements. New
unit test cases are generally a good thing. Bug fixes are great. Send your
changes as patches (created using cvs diff -u) to this list and if they
conform to the coding standards and are high quality, someone is likely to
commit them.

Always make sure the build (ant clean all) is successful before you send
any patch and eye-ball the patch to look for things like tabs which should
be multiple spaces, lines over 80 characters long, and material which is
not relevant to the patch but which has crept in. The best patches are
localised changes which preserve the modularity of the classes they modify.

Hope that helps.

Glyn


Mime
View raw message