Sounds great ! We need a new Maven based build script for release process , I will look in to this.
BTW so far Lawrence manage the release process as the release manager . Lawrence , do you have any time to manage this release ? If not any one have any other suggestions ? Thanks, On Fri, Oct 23, 2009 at 1:55 AM, Arthur Ryman <[email protected]>wrote: > +1 > > > On Thu, Oct 22, 2009 at 11:04 AM, Lawrence Mandel <[email protected]>wrote: > >> >> I agree that Woden is due for a release. +1 >> >> Lawrence >> >> >> >> >> From: Jeremy Hughes <[email protected]> To: [email protected] >> Date: 10/22/2009 06:04 AM Subject: Re: Woden 1.0 Milestone 9 release Sent >> by: [email protected] >> ------------------------------ >> >> >> >> +1 >> >> 2009/10/22 Sagara Gunathunga <[email protected]>: >> > Hi all, >> > >> > During the recent past we have introduced following features to Woden. >> > >> > 1.) Woden serialization feature based on both DOM and OM. >> > 2.) WSDL2.0 components level equals method. >> > 3.) Woden no longer depend on Xerces , possible to switch with any >> > JAXP implementation. >> > 4.) Woden logging strategy. >> > 5.) Maven plugin for Woden WSDL converter >> > 6.) New Maven friendly directory structure. >> > >> > >> > Also other than above , after the milestone 8 release Woden team have >> > resolved following JIRA issues. >> > >> > 1.) (WODEN-224) Dependencies should refactor among modules. >> > 2.) (WODEN-208) Provide simple error message if user tries to parse >> WSDL 1.1 >> > 3.) (WODEN-182) Private QName class causes classloading issues >> > 4.) (WODEN-57) Use ws-commons-java5 for QName class >> > 5.) (WODEN-220) OMWSDLReader should support to read from WSDLSource. >> > 6.) (WODEN-211) Refactor directory layout to be more Maven compliant >> > 7.) (WODEN-170) mvn pom.xml to download test-suite.zip from W3C >> > 8.) (WODEN-181) getInterfaceMessageReferenceElement() method >> > required on BindingMessageReferenceElement >> > 9.) (WODEN-74) Validation does not report a QName resolution error >> > for the {interface fault} property of InterfaceFaultReference >> > 10.) (WODEN-194) Change isSafety() method to isSafe() >> > 11.) (WODEN-195) Improve formatting of messages with no message >> parameters >> > 12.) (WODEN-192) schemaLocation URI not resolved correctly using jar >> files >> > 13.) (WODEN-191) URISyntaxException in SimpleURIResolver when path >> > contains spaces >> > 14.) (WODEN-189) NPE when interface extension used with Element API >> > 15.) (WODEN-179) Remove WSDLReader.readWSDL methods that take an >> > ErrorHandler parameter >> > 16.) (WODEN-178) DescriptionImpl methods addElementDeclaration and >> > addTypeDefinition should not be public >> > 17.) (WODEN-177) Share client-configurable objects across the Woden >> > implementation >> > 18.) (WODEN-176) Remove the setParentElement method from the API >> > 19.) (WODEN-175) ImportElement and IncludeElement should extend >> NestedElement >> > 20.) (WODEN-173) Correct the WSDL object model implementation >> inheritance >> > 21.) (WODEN-174) Include the prefix in QNames from the target namespace >> > 22.) (WODEN-36) Maven build system for Woden >> > >> > >> > >> > IMO at this point we can think about Woden milestone 9 release, WDYT ? >> > >> > >> > >> > Thanks , >> > >> > >> > -- >> > Sagara Gunathunga >> > >> > Blog - http://ssagara.blogspot.com >> > Web - >> > http://people.apache.org/~sagara/<http://people.apache.org/%7Esagara/> >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: [email protected] >> > For additional commands, e-mail: [email protected] >> > >> > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> >> >> > -- Sagara Gunathunga Blog - http://ssagara.blogspot.com Web - http://people.apache.org/~sagara/
