Simon, I have made these changes, thanks. I am unsure of one thing regarding the difference between CHANGES and RELEASE_DOCUMENTATION. These files were provided by Yang as a JIRA attachment in consultation with Frank, and I had been meaning to check the difference in purpose of the two files. I can't see any apache documentation to say that we need both, so as Yang and Frank are currently tucked up in bed I imagine, I am making the assumption that CHANGES.txt is a running log that is used in the production of any given release. If this is wrong then I'll need to fix that, but currently my fix for your catch is to put a note at the top of CHANGES.txt to explain its purpose and direct the user of a new release to look at the RELEASE_NOTES.txt file.
Regards , Kelvin. On 13/10/06, kelvin goodson <[EMAIL PROTECTED]> wrote:
Thanks for all these good catches, will fix. Kelvin. On 12/10/06, Simon Nash <[EMAIL PROTECTED]> wrote: > > This is getting very close now. Good work! I have a few minor > comments, mostly typos in the samples documentation. > > in sample/README.txt > > change "already build" to "already built" > > in sample/src/main/java/org/apache/tuscany/samples/sdo/overview.html > > change Samples Programs to Sample Programs > remove misplaced line breaks on penultimate lines of Overview and > Experimentation > sections > "third category" in Overview paragraph does not match the categories > in the > table that precedes this text when this file is displayed within > sample/site/apidocs/index.html (it's actually a subset of the first > category in the table). An easy fix is to change "and the third > category were" > to "or were" > in the "Getting Ready ..." section, first line, change "depend of" to > "depend on" > in the "Getting Ready ..." section, second last paragraph, first line, > change > "insrtuctions" to "instructions" > download link for the SDO 2.01 specs currently points to the IBM web > site and should > be changed to point to the osoa.org site > > in sample/site/apidocs/org/apache/tuscany/samples/sdo/package.html > > fix dangling reference at the end of this file > > in > sample/site/apidocs/org/apache/tuscany/samples/sdo/otherSources/package.html > > > in first sentence, change "specification" to "SDO Specification" (to > avoid forward reference when this text is displayed in the package overview > table in sample/site/apidocs/index.html) > change "usefull scnearios" to "useful scenarios" > download link for the SDO 2.01 specs currently points to the IBM web > site and should > be changed to point to the osoa.org site > > in > sample/site/apidocs/org/apache/tuscany/samples/sdo/specCodeSnippets/package.html > > > change "snipets" to "snippets" (twice) > change "flexability" to "flexibility" > change "desireable" to "desirable" > change "extend or improve" to "to extend or improve" > download link for the SDO 2.01 specs currently points to the IBM web > site and should > be changed to point to the osoa.org site > > in > sample/site/apidocs/org/apache/tuscany/samples/sdo/specExampleSection/package.html > > > change "specification, exceptions" to "specification; exceptions" > download link for the SDO 2.01 specs currently points to the IBM web > site and should > be changed to point to the osoa.org site > > in output from ExecuteSamples, CreatePurchaseOrder, and > ReadPurchaseOrder: > > change "Fuhwei Lo" to "Fuhwei Lwo" > > in SDO binary distribution > > there is duplication of content between RELEASE_NOTES.txt and > CHANGES.txt > > > Thanks. > > Simon > > kelvin goodson wrote: > > > I have put a new release candidate for SDO Java up at > > http://people.apache.org/~kelvingoodson/sdo_java/RC3/<http://people.apache.org/%7Ekelvingoodson/sdo_java/RC3/> > > > > This tries to take into account the comments that the sample > distribution > > does not need to be stand alone, and that > > javadoc should be shipped with the binary and sample distributions. > > > > I have been fighting with the maven build environment to produce a > good set > > of javadoc as part of the build, from a user's > > perspective, but that's not at all easy given the structure of our > > projects > > and the nature of the maven javadoc plugin, > > so currently the binary distribution carries javadoc for the sdo api > and > > all of the tuscany implementation. The README file > > draws the attention of an SDO user to relevant classes in > the tuscany > > implementation javadoc. > > > > Regards, Kelvin. > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
