Jochen Wiedmann wrote:
What's the problem? I can't see anyone from preventing an Axis2/C
committer being a
Axis2/Java committer as well, if he or she is interested in it? My
expectation would be,
though, that it is a minority only, who wants it.
Jochen
It could be small community compared to Axis2/Java community. But still
it is an active community and ppl use Axis2/C for useful things. By the
foregoing discussions I don't see any significant gain to the Axis2/Java
community by making Axis2/C orphaned. So far there has been no problem
being them together in the same svn code base so why bother now for no
seemingly valid reason? Absolute -1 for making Axis2/C and Axis2/Java
separate. Actually being together it has always been a strength at least
for Axis2/C while it does not weaken Axis2/Java. Actually I have heard
some proposals of combined solutions using both Axis2/Java and Axis2/C.
thanks,
Damitha
--
__________________________________________________________________
Damitha Kumarage
http://people.apache.org/
__________________________________________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
