It seems to me to make sense to keep these shared items in a commons project for now, thought if it was otherwise sitting on the sidewalk holding out a cup, I could make an argument for hosting it in CXF. These guys may all even share a certain set of techological problems involving complex data structures and multiple representations.
Were I a member of the ASF, I might be wondering if there is some structural novelty that would make sense for code that is deeply interesting to multiple projects and not that useful by itself. For example, we could have a scheme wherein all CXF and Axis committers were 'ex-officio' committers on XmlSchema. A sort of a DMZ. On Mon, Nov 3, 2008 at 10:32 AM, Davanum Srinivas <[EMAIL PROTECTED]> wrote: > ok. i agree now. > > thanks, > dims > > On Mon, Nov 3, 2008 at 10:30 AM, Daniel Kulp <[EMAIL PROTECTED]> wrote: >> On Monday 03 November 2008 10:14:30 am Davanum Srinivas wrote: >>> Glen, >>> >>> Was looking at >>> http://wiki.apache.org/ws/FrontPage/Proposals/Axis2TLPProposal >>> >>> Any thoughts on why leave behind XmlSchema, Neethi, Axiom? >> >> Because they are used by several other projects that have nothing to do with >> Axis 2? >> >> >>> >>> Reasons why: >>> - Very few people are working on these 3 projects >>> - Any changes to these 3 projects needs almost immediate changes in Axis2 >> >> As well as CXF, ServiceMix, etc... Maybe they should go into CXF or >> ServiceMix instead? (that was just to make a point, not a serious question) >> >> >>> - We have almost always synced up the releases of these 3 projects >>> lock step with Axis2 releases. >>> - IMHO, they can't survive as a TLP right at this moment. >> >> No, but keeping them in "ws commons" makes sense since they are used by >> projects other than Axis2. >> >> -- >> Daniel Kulp >> [EMAIL PROTECTED] >> http://dankulp.com/blog >> > > > > -- > Davanum Srinivas :: http://davanum.wordpress.com >
