Dan, Nice work on the documentation. Overall it's very good. If you have time before you finish up this week can you clarify the 2 areas below in the build section:
1. I don't think the statement "Runs every build target below" is very clear. Do you mean the targets below in the build.xml file? The documentation should be readable on its own. I think a simple statement like the following is better for consumers of this information. buildAll - Builds all Woden packages (API, DOM, and OM) The top level ant targets we have and their uses are :- buildAll - Runs every build target below. buildAndTestAll - Runs every build target below then runs all the test targets as explained in the Testing section. distBuild - Runs buildAll then creates the compressed archives for the distributions we have. buildAPI - Runs every build target below. buildDOM - Runs every build target below. buildOM - Runs every build target below. 2. I think a few sentences about why Woden builds API, DOM and OM packages would be useful as an introduction to the build process on Woden packaging before getting into the build technologies. I'll take a pass at this next week to correct any grammar or spelling mistakes and perhaps elaborate a bit. After this documentation is committed we just have one section left to fill in: Source Code. Lawrence "Dan Harvey" <[EMAIL PROTECTED]> 09/18/2007 06:56 AM Please respond to [email protected] To [email protected] cc Subject Re: Woden development process doc Lawrence, Yes its does include both points, but I've just tired to find where in Jira I've attached the patch for the site and can't seem to find it.. So I've created the patch again from my source and attached it to Woden-67, also reading it though again I've added a few lines about making sure you run the tests and how to add too both of the test suites. If you want to read through it before its committed its here: https://issues.apache.org/jira/secure/attachment/12366083/site.patch Thanks, Dan On 17/09/2007, Lawrence Mandel <[EMAIL PROTECTED]> wrote: Arthur, Good suggestions. Dan has written up a testing section that needs to be added to the process doc. Dan - Does your testing section cover the two items Arthur suggested below? If not, can you work them in? Thanks, Lawrence "Arthur Ryman" <[EMAIL PROTECTED]> 09/16/2007 10:49 PM Please respond to [email protected] To [email protected] cc Subject Re: Woden development process doc Lawrence, I was looking at the Testing section of the dev process. I suggest it include the following (this is just an outline - the details need to be filled in): 1. There is a suite of JUnit tests. These should be run before committing any new code or fixes. You should add tests to this suite to cover any new code or fixes. 2. There is an Ant task, validatewsdl20, (class org.apache.woden.ant.ValidateWSDL20, see the ant-test directory for build.xml) that runs Woden against a set of WSDL 2.0 documents. This task should be run against the W3C Test Suite. The results include a set of generated Component Model Interchange format XML documents, and a report that contains any violated Assertions. These results can be compared against the expected results by running scripts provided by the W3C. The results can also be posted to the W3C WSDL 2.0 Web site to advertised progress as an implementation of the WSDL 2.0 spec. New test cases may be added to the W3C Test Suite by submitting then to the W3C Bugzilla system. On 8/27/07, Lawrence Mandel <[EMAIL PROTECTED]> wrote: > Thanks for pointing out the incorrect link Sagara. The link was wrong on > the Woden status page as well. I've corrected both and they will be > visible the next time the site is refreshed. (This happens every few > hours.) > > Lawrence > > > > > "Sagara Gunathunga" <[EMAIL PROTECTED]> > 08/27/2007 01:50 AM > Please respond to > [email protected] > > > To > [email protected] > cc > > Subject > Re: Woden development process doc > > > > > > > Hi Lawrence, > I have notice that there is a small error with projectsusingwoden page > [1]. The link Apache Axis2 is not reference to the correct location. It > also reference to Apache ServiceMix project. > > [1] http://incubator.apache.org/woden/projectsusingwoden.html > > Thanks > Sagara > Blog - ssagara.blogspot.com > > > On 8/22/07, Lawrence Mandel <[EMAIL PROTECTED]> wrote: > I've made some further updates to the Woden development process document > [1]. There are three TBD items currently in the document. > > 1. TBD: Fill in details about Java coding conventions. > 2. TBD: Insert details about how to test Woden > 3. TBD: Insert details of the Woden build process > > John, I'm hoping you can handle 1. No rush on this. > > Dan has already written content for 2 and 3 that will be added to the > document shortly. > > I would appreciate a review of the content by the Woden team and > community. Specifically, are there any topics that are not present, any > topics that require further elaboration, and any topics that require > correction. > > Thanks, > > Lawrence > > [1] http://incubator.apache.org/woden/dev/devprocess.html > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > -- > Sagara Gunathunga > > Blog - ssagara.blogspot.com > > > --------------------------------------------------------------------- > 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] --------------------------------------------------------------------- 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]
