Azeez,
unit test for just what broke..not for everything. Little tests over a period
of time will add up.
To state the obvious, All along it's been the same set of people making changes in multiple code bases here in apache
and else where, now that more folks are pitching in, there is more churn and more potential for breakage.
Yes, +1 to "don't want to make life complicated for everyone".
Yes, we should be more careful about deprecating things.
thanks,
dims
On 08/20/2009 10:01 AM, Afkham Azeez wrote:
Creating a unit test is one thing which we can do, but Axis2 has so
many public methods, and it is not reasonable at this moment to ask
anybody to create unit tests for each of these public methods. I guess
there is a purpose in the widely used practice of deprecating methods.
Imagine if the other projects that we widely use make such ad-hoc API
changes, and when we complain, if they ask us to write a unit test for
their APIs; it is not reasonable. We do not want to make life
complicated for everybody.
Azeez
On Thu, Aug 20, 2009 at 12:49 PM, Davanum Srinivas<dava...@gmail.com> wrote:
Azeez,
Do you mind creating a unit test(s) for the behavior/API(s) you need? That
would help keep desired behavior and enforce that what you need will not be
modified.
thanks,
dims
On 08/20/2009 07:45 AM, Afkham Azeez wrote:
Yes Dims. However, if everybody continues to merrily change APIs,
making public methods private& so on, things are going to become a
big mess. Axis2 provides public APIs, and those may be having
problems, but still they are public APIs. This is why you have to be
very careful when defining APIs; if you get them wrong, you may have
to live with it for a long time.
Azeez
On Thu, Aug 20, 2009 at 11:38 AM, Davanum Srinivas<dava...@gmail.com>
wrote:
Azeez,
We are still following, commit-then-review right?
thanks,
dims
On 08/20/2009 07:33 AM, Afkham Azeez wrote:
Hi Andreas,
The changes you've done to the APIs as per
https://issues.apache.org/jira/browse/AXIS2-4465 badly breaks some of
the projects that depend on Axis2. Please revert this, and please
engage the community before making such drastic changes in the future.
