Hi all , A couple of weeks ago i have fixed WODEN -170 and now there is no any problem with WODEN -211 branch ,so we can start merging process starting from 211 branch.
I want to know is somebody already started this merging process if not any volunteer for this ? Thanks, On Fri, Jul 17, 2009 at 10:08 PM, Lawrence Mandel<[email protected]> wrote: > > My message below has bounced back twice with Apache's mail server thinking > it's spam. Oh well, thought I'd try again with a new message. > > > Woden has been fairly dormant for a while now. Part of this is related to > other priorities (work, family, school, etc.) for John and myself. I think a > large part is the lack of adoption of WSDL 2.0 and by extension Woden. At > this point I think we should ask whether it is worth investing more time in > this project or merging the contents that Sagara has listed below, cutting a > release that incorporates these changes, and putting the project in > maintenance mode. If interest is there (from Sagara, Jeremy, anyone else) to > continue developing Woden I suggest we find a new project leader to drive > development as I have not had time to contribute to this project. > > Jeremy - My memory tells me that Sagara has already contributed a fair > amount to Woden. It may be appropriate to nominate him for committer status. > > And, I'm +1 to all the changes listed below. > > Lawrence > > > From: Sagara Gunathunga <[email protected]> > To: [email protected] > Date: 07/16/2009 01:16 PM > Subject: Woden development > > ________________________________ > > > Hi All , > > Since we haven't done any major development recently i like to propose > following plan to restart our works on Woden. > > please go ahead and add/modify/remove item to this list, I just want > to take a initiative for this task. appreciate for any of your > comments. > > > Task List > ====================================== > > (1) Merge Maven compliant directory layout (211) branch to the trunk. > > I have found some of the issues with Jeff Maury's original > contribution and required modifications were attached with the JIRA > issue WODEN -211. Still there is a small issue with ruining few W3C > TestCases through Maven ant plug-in. At the moment I'm looking in to > that, once i finish i will update the WODEN - 170 . (Seems WODEN - 170 > is much more related to this). > Once we have a fix for WODEN - 170 , we can merge 211 branch to the > trunk safety. > > > (2) Merge components level equals method (209) branch into the trunk. > > Since this is completed by John, now we can merge in to the > trunk. This feature will simplify lot of test cases such as > WSDLReader/Writer test cases. > > (3) Merge serialization (65) branch. > > Since Woden serialization (JIRA -65) is almost completed for both DOM > and OM we can merge it in the trunk. > > > (4) Remove Xrecees dependency from Woden. > > I have resolved WODEN-152 issue and now we can remove Xrecees > parser dependency from Woden. > > (5) Commit some of the resolved issues in to the trunk. > > (a) WODEN-220 - OMWSDLReader should support to read from WSDLSource. > > (b) WODEN-182 - Private QName class causes classloading issues > > (c) WODEN-103 - Woden is failing several binding assertions in > the WSDL validation report > > (d) WODEN-103 - Provide simple error message if user tries to > parse WSDL 1.1 > > > (6) Future direction > > (a) WODEN-72 - OASIS-style URI Resolver > (b) WODEN-170 - mvn pom.xml to download test-suite.zip from W3C > (c) Updating OM implem > > ( I'm already stated to works on above 3 issues , if any one else > working on any other areas please add them too ) > > > > > Thanks , > > > -- > Sagara Gunathunga > > Blog - http://ssagara.blogspot.com > Web - http://sagaras.awardspace.com/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > > > -- Sagara Gunathunga Blog - http://ssagara.blogspot.com Web - http://sagaras.awardspace.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
