I guess this is the question about what should we call the next release - M3 or beta1 or something else? See: http://mail-archives.apache.org/mod_mbox/ws-tuscany-dev/200704.mbox/[EMAIL PROTECTED]
...ant On 4/29/07, 王洪伟 <[EMAIL PROTECTED]> wrote:
why not with a sign --M3 ? like this : tuscany-sca-1.0-M3-beta1.zip tuscany-sca-1.0-M3-beta1.tar.gz tuscany-sca-1.0-M3-beta1-src.zip tuscany-sca-1.0-M3-beta1-src.tar.gz 2007/4/29, ant elder <[EMAIL PROTECTED]>: > > 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-srcwith > 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. > > ...ant >
