[Fwd: Re: [Axis2] Removing old client side code from main source tree]

[Deepal Jayasinghe <de...@opensource.lk>]

Deepal ..I think you should ask the user list is lot of people using
it. If people had moved to service client you do not need to move them
to scracth .. just delete them.  (But judging by the work I had to do
in moving to service client .. I belive there are lot still using it)

Srinath

On 3/9/06, Deepal Jayasinghe <de...@opensource.lk> wrote:

> Hi all;
>
> As you know in the current SVN we have our old client side codes (Call
> , InOutMEPClient etc..) and no body is using those, in fact they are
> marked as deprecated.
> So what if we move them to scratch area , keeping them in the main
> source tree make no sense to me :)
>
> here is my +1 for moving them away from Axis2 main tree , and I like
> to do that before next release.
>
> ????????????????
>

--
============================
Srinath Perera:
   http://www.cs.indiana.edu/~hperera/
   http://www.bloglines.com/blog/hemapani



-- 
Thanks,
Deepal
................................................................
~Future is Open~

Re: [Fwd: Re: [Axis2] Removing old client side code from main source tree]

[Eran Chinthaka <ch...@opensource.lk>]

Moving to scratch area is a bad idea, IMO. You should either have it or
delete it. I prefer to remove them in this release. Else, if there are
bugs in Call, we may have to fix them as well.

+1 remove them.
0- to move to scratch.

Chinthaka

>
>On 3/9/06, Deepal Jayasinghe <de...@opensource.lk> wrote:
>
>  
>
>>Hi all;
>>
>>As you know in the current SVN we have our old client side codes (Call
>>, InOutMEPClient etc..) and no body is using those, in fact they are
>>marked as deprecated.
>>So what if we move them to scratch area , keeping them in the main
>>source tree make no sense to me :)
>>
>>here is my +1 for moving them away from Axis2 main tree , and I like
>>to do that before next release.
>>
>>????????????????
>>
>>    
>>
>
>--
>============================
>Srinath Perera:
>   http://www.cs.indiana.edu/~hperera/
>   http://www.bloglines.com/blog/hemapani
>
>
>
>  
>