As a Axis2/C and WSDL2C(Axis2/Java) contributor, I am -1 on discouraging TLP for both Java and C versions. Why you suggest to separate them if they share the same architecture and some tools. Say in case Axis2/C is not in common TLP, will Axis2/C become a separate TLP? I think common TLP is the best thing in case we make Axis2 a TLP.
Thanks, Milinda On Thu, Oct 30, 2008 at 4:04 PM, Jochen Wiedmann <[EMAIL PROTECTED]>wrote: > On Tue, Oct 28, 2008 at 4:02 AM, Glen Daniels <[EMAIL PROTECTED]> > wrote: > > > * Axis2 - becomes a TLP for both Java and C versions, with > > Axis2-specific components underneath as subprojects. So Rampart, > > Sandesha, Savan, Kandula.... > > I'd discourage a common TLP for both Java and C versions. > > I know this is the usual behaviour in a lot of other projects (Xerces, > Log4j, to name a few). However, I think that the most important aspect > of a TLP is a community. A community = one community, not two > communities. IMO, the common denominator between Axis C and Axis Java > is quite small and not worth bothering. Otherwise we'd simply have the > next umbrella. > > Jochen > > > -- > I have always wished for my computer to be as easy to use as my > telephone; my wish has come true because I can no longer figure out > how to use my telephone. > > -- (Bjarne Stroustrup, > http://www.research.att.com/~bs/bs_faq.html#really-say-that<http://www.research.att.com/%7Ebs/bs_faq.html#really-say-that> > My guess: Nokia E50) > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- http://mpathirage.com http://wso2.org "Oxygen for Web Service Developers" http://wsaxc.blogspot.com "Web Services With Axis2/C"
