On Mon, 2006-10-02 at 06:09 -0500, Srinath Perera wrote:
> +1 !! and may be we should keep adding the best practises to developer
> guide .. to make sure they are kept track of
Excellent idea! Thanks for volunteering ;-).
Sanjiva.
axis-dev@ws.apache.org
>
>
>
> To
> axis-dev@ws.apache.org
> cc
>
> Subject
> Re: [Axis2] Adding revision number while resolving issues
>
>
>
>
>
>
>
>
>
> Hello All,
>
> I think it is a g
CTED]
Jeff Barrett/Austin/[EMAIL PROTECTED]
10/02/2006 07:47 AM
Please respond to
axis-dev@ws.apache.org
To
axis-dev@ws.apache.org
cc
Subject
Re: [Axis2] Adding revision number while
resolving issues
Hello All,
I think it is a great idea to have the svn revision in th
ev@ws.apache.org
cc
Subject
[Axis2] Adding revision number while
resolving issues
Hi,
When you fix a bug and resolve a JIRA, let's make it a best practice to
include the revision number in the comment you put while resolving the
JIRA.
I'm now trying to fix a bug related ele
+1 !! and may be we should keep adding the best practises to developer
guide .. to make sure they are kept track of
On 10/2/06, Eran Chinthaka <[EMAIL PROTECTED]> wrote:
Hi,
When you fix a bug and resolve a JIRA, let's make it a best practice to
include the revision number in the comment you pu
Hi,
When you fix a bug and resolve a JIRA, let's make it a best practice to
include the revision number in the comment you put while resolving the
JIRA.
I'm now trying to fix a bug related elementFormDefault="qualified", but
seems this was fixed earlier by Ajith. But when I use the current build
