ant elder wrote:
On 4/29/07, ant elder <[EMAIL PROTECTED]> wrote:
What do we want the Tuscany SCA distribution to look like for the next
release? I'll suggest the following straw man as start, please suggest
changes. I'm using the name 'beta1' here till we decide on the real
name.
All the artifacts in the default build would be published to the maven
repository, and there'd be two downloadable distributions, a source and
binary:
tuscany-sca-1.0-beta1.zip
tuscany-sca-1.0-beta1.tar.gz
tuscany-sca-1.0-beta1-src.zip
tuscany-sca-1.0-beta1-src.tar.gz
The binary unzips to a directory named tuscany-sca-1.0-beta1 with the
following contents:
tuscany-sca-1.0-beta1
- DISCLAIMER
- LICENSE
- NOTICE
- release-notes.txt
+ javadoc
- the OSOA SCA API Javadoc
- the Tuscany SPI Javadoc
+ lib
- tuscany-sca-beta1.jar (this is all the tuscany-*.jars munged
into
a single jar)
- tuscany-sca-manifest-beta1.jar (this is an empty jar with just a
manifest which has all the tuscany and dependent jars in the manifest
classpath)
- (all the other dependency jars - stax, jetty, axis2 etc)
+ modules
- (each individual Tuscany module jar)
+ samples
- (all the samples)
How should the samples work, should there be ant or mvn build scripts
for
each sample? Should there be pre-build sample jars in the binary distro?
The src distro unzips to a directory named tuscany-sca-1.0-beta1-src
with
the following contents:
tuscany-sca-1.0-beta1-src
- BUILDING
- DISCLAIMER
- LICENSE
- NOTICE
+ distribution
+ itest
+ modules
+ samples
There's now a sca\distribution folder which has build scritps to create
the above to try this out.
This should be working now so running mvn in sca\distribution should
create
the distributions in the sca\distribution\target directory. The binary
distro should work to run all the samples, eg, unzip the binary distro
somewhere and then change into the directory
tuscany-sca-1.0-incubating-SNAPSHOT\samples\calculator and from there you
should be able to run a sample with:
java -cp target\tuscany-sample-calculator-1.0-incubating-SNAPSHOT.jar
;..\..\lib\tuscany-sca-manifest-1.0-incubating-SNAPSHOT.jar
calculator.CalculatorClient
...ant
Ant,
I built and took a look at the distribution. It looks very good to me. I
like the overall structure and the idea of providing as an option a
single JAR for Tuscany.
I have a few questions and suggestions.
- tuscany-sca.jar contains .svn directories, I guess they should be
removed from the JAR.
- Also 2 empty xsds at the root of the JAR and com.example packages,
they must be coming from one of the examples?
- I guess we're going to rename this to sca-1.0-beta1-incubating?
- Like you said above, we'll have to include the javadoc for our SPIs.
- How did you produce the single META-INF/services/...ModuleActivator
file? is it generated?
- We have two different servlet-api JARs, should we pick one?
- Could we have, in the bin distro, a tuscany-sca-src.jar containing all
the source code for the classes in tuscany-sca.jar?
- How about renaming tuscany-sca.jar to tuscany-sca-all.jar, or any name
indicating that it's all the tuscany code?
- The NOTICE will have to be updated as it contains obsolete dependencies.
- I think it would be great to have Ant build scripts for some of the
samples, as not everybody is using Maven.
- Pre-built sample JARs would be great too, but not as important if we
have a simple Ant build for the samples.
Thanks!
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
