Simon
  thanks very much for these points.  I will investigate implementing your
alternative suggestion for the sample ditribution organisation.

I'll also take a look at adding javadoc into the binary distribution.  I'm
not sure how easy it will be to get the build to produce a subset of javadoc
for the implementation projects.  It's clear that we would want javadoc for
the sdo-api project,  but for the tools project we would want
XSD2JavaGenerator etc, and for the impl project we would want SDOUtil etc.
If I can find out how to configure javadoc to build just a subset of files
then I'll do that.  If I can't do that in the time available I propose
shipping full javadoc for the projects,  but including an overview that
directs an SDO user to the pertinent classes.

Regards, Kelvin.

On 05/10/06, Simon Nash <[EMAIL PROTECTED]> wrote:

I was surprised to see a large subset of the jars in the SDO binary
distribution duplicated within the samples distribution.  This seems
redundant given that I (and presumably most SDO users) will have not
only downloaded the samples but also downloaded the full set of
SDO jars in the binary distribution.

An alternative that seems more logical and convenient would be for
the samples distribution to contain only the samples, in a directory
structure that can be overlaid on the directory structure produced
by the unzipped SDO binary distribution.  So users who want both the
binary distribution and the samples would create a target directory,
unzip the binary disitrbution into that directory, and then unzip
the samples distribution into the same directory.

I was also surprised that there is javadoc in the samples
distribution but no javadoc (or documentation of any kind) in the
binary distribution.  I was expecting the binary distribution to be
an SDK for SDO users (application developers), containing javadoc
for the SDO APIs together with other developer documentation
(e.g., how to run XSD2JavaGenerator).  It seems undesirable to
require developers to have internet connectivity in order to
access this documentation.

   Simon

kelvin goodson wrote:

> I have made available an RC2 release candidate for SDO for Java at
> http://people.apache.org/~kelvingoodson/sdo_java/RC2/
>
> The main differences from RC1a are
>
> Tuscany JIRAs 115 and 755 are fixed
> The source distribution has been split (re-split) into specification and
> implementation archives after discussion on the tuscany-dev mailing list
> The samples are distributed as a separate standalone archive containing
> sample source code, java doc and all required binary artifacts.
> The EMF dependency jar is now the non-snapshot 2.2.1 version.
>
> Best Regards, Kelvin.
>



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Reply via email to