You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by ant elder <an...@gmail.com> on 2007/04/29 10:21:17 UTC
Next SCA release distributions
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.
...ant
Re: Next SCA release distributions
Posted by Jean-Sebastien Delfino <js...@apache.org>.
Simon Laws wrote:
> On 5/2/07, Jean-Sebastien Delfino <js...@apache.org> wrote:
>>
>> [snip]
>> Simon Laws wrote:
>> >
>> >> - tuscany-rmi? Should this be a binding
>> >>
>> >>
>> >> Yes, would be better as tuscany-binding-rmi.
>> >>
>>
>> We already have a tuscany-binding-rmi module: the implementation of the
>> RMI binding.
>>
>> The tuscany-rmi module defines an RMI hosting extension point, similar
>> to how the tuscany-http module provides an HTTP host extension point.
>>
>> To make that clear, I'd suggest to rename tuscany-rmi to
>> tuscany-host-rmi and tuscany-http to tuscany-host-http.
>>
>> --
>> Jean-Sebastien
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>>
>> You are right. I didn't spot that. I must be going blind. Agree with the
> move to using host in the name.
>
> Simon
>
Ok, I'll do that rename some time later today then.
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
Re: Next SCA release distributions
Posted by Simon Laws <si...@googlemail.com>.
On 5/2/07, Jean-Sebastien Delfino <js...@apache.org> wrote:
>
> [snip]
> Simon Laws wrote:
> >
> >> - tuscany-rmi? Should this be a binding
> >>
> >>
> >> Yes, would be better as tuscany-binding-rmi.
> >>
>
> We already have a tuscany-binding-rmi module: the implementation of the
> RMI binding.
>
> The tuscany-rmi module defines an RMI hosting extension point, similar
> to how the tuscany-http module provides an HTTP host extension point.
>
> To make that clear, I'd suggest to rename tuscany-rmi to
> tuscany-host-rmi and tuscany-http to tuscany-host-http.
>
> --
> Jean-Sebastien
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>
> You are right. I didn't spot that. I must be going blind. Agree with the
move to using host in the name.
Simon
Re: Next SCA release distributions
Posted by ant elder <an...@gmail.com>.
On 5/2/07, Jean-Sebastien Delfino <js...@apache.org> wrote:
>
> [snip]
> Simon Laws wrote:
> >
> >> - tuscany-rmi? Should this be a binding
> >>
> >>
> >> Yes, would be better as tuscany-binding-rmi.
> >>
>
> We already have a tuscany-binding-rmi module: the implementation of the
> RMI binding.
>
> The tuscany-rmi module defines an RMI hosting extension point, similar
> to how the tuscany-http module provides an HTTP host extension point.
>
> To make that clear, I'd suggest to rename tuscany-rmi to
> tuscany-host-rmi and tuscany-http to tuscany-host-http.
+1 to changing to tuscany-host-rmi and tuscany-host-http
But we also have a tuscany-host-spi and tuscany-host-embedded which have
nothing to do with and aren't used by tuscany-host-rmi and
tuscany-host-http, could these be renamed to something like tuscany-host-spi
be tuscany-runtime-spi and tuscany-host-embedded be
tuscany-runtime-embedded?
If there's going to be any module name changes then the package name used
withing the module will also have to be renamed right? So how about starting
to change things to org.apache.tuscany.sca at the same time?
And vaguely related, everywhere we have a dependency on
tuscany-host-embedded we also have a dependency on
tuscany-implementation-java-runtime, how about to simplify things (eg for
the sample pom's) we add tuscany-implementation-java-runtime as a dependency
in tuscany-host-embedded?
...ant
Re: Next SCA release distributions
Posted by Jean-Sebastien Delfino <js...@apache.org>.
[snip]
Simon Laws wrote:
>
>> - tuscany-rmi? Should this be a binding
>>
>>
>> Yes, would be better as tuscany-binding-rmi.
>>
We already have a tuscany-binding-rmi module: the implementation of the
RMI binding.
The tuscany-rmi module defines an RMI hosting extension point, similar
to how the tuscany-http module provides an HTTP host extension point.
To make that clear, I'd suggest to rename tuscany-rmi to
tuscany-host-rmi and tuscany-http to tuscany-host-http.
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
Re: Next SCA release distributions
Posted by Paulo Henrique Trecenti <pt...@gmail.com>.
Hi,
I believe that it is better to wait until having a more consistent version
of what already it is.
2007/5/2, ant elder <an...@gmail.com>:
>
> On 5/2/07, Simon Laws <si...@googlemail.com> wrote:
> >
> > On 5/2/07, ant elder <an...@gmail.com> wrote:
> > >
> > > On 5/2/07, Simon Laws <si...@googlemail.com> wrote:
> > > >
> > > > On 4/30/07, ant elder <an...@gmail.com> wrote:
> > > > >
> > > > > Excellent thanks, thats type type feedback I was looking for!
> > Comments
> > > > in
> > > > > line...
> > > > >
> > > > > On 4/30/07, Jean-Sebastien Delfino <js...@apache.org> wrote:
> > > > >
> > > > > <snip/>
> > > > >
> > > > > I have a few questions and suggestions.
> > > > > > - tuscany-sca.jar contains .svn directories, I guess they should
> > be
> > > > > > removed from the JAR.
> > > > >
> > > > >
> > > > > I can't see these, i could just be blind or maybe its something
> > > > different
> > > > > about our environments could you give an example of what the file
> > > names
> > > > > are?
> > > > >
> > > > > - Also 2 empty xsds at the root of the JAR and com.examplepackages,
> > > > > > they must be coming from one of the examples?
> > > > >
> > > > >
> > > > > The com.example.* files are coming from the databinding-jaxb and
> > > > > databinding-sdo modules, we need to fix those modules but I'm not
> > sure
> > > > > how.
> > > > > It looks like the jaxb and sdo plugins need to some way to say
> > they're
> > > > > test
> > > > > resources. Any one know how to fix this?
> > > > >
> > > > > I can't see the 2 empty xsds, something different about our
> > > environments
> > > > > again?
> > > > >
> > > > > - I guess we're going to rename this to sca-1.0-beta1-incubating?
> > > > >
> > > > >
> > > > > Yes, the name should be being picked up from the pom, but i'll
> test
> > it
> > > > > does
> > > > > change. (Using the current format the name would be
> > > 1.0-incubating-beta1
> > > > ,
> > > > > do
> > > > > we really want 1.0-beta1-incubating?)
> > > > >
> > > > > - Like you said above, we'll have to include the javadoc for our
> > SPIs.
> > > > >
> > > > >
> > > > > Yes, I guess I can add that in now even though the SPIs aren't
> done
> > by
> > > > > just
> > > > > including the tuscany-core-spi module javadoc. Is javadoc for just
> > > these
> > > > > two
> > > > > modules enough (sca-api and core-spi). I've added this now, are
> > there
> > > > > other
> > > > > modules we want javadoc for?
> > > > >
> > > > > - How did you produce the single
> > META-INF/services/...ModuleActivator
> > > > > > file? is it generated?
> > > > >
> > > > >
> > > > > This is done in the java/sca/distribution/bundle project using the
> > > Maven
> > > > > Shade plugin, see in the pom.xml the shade config where a Shade
> > > > > AppendingTransformer is used to merge all the ModuleActivator
> files
> > > into
> > > > > one. No doc at all about the Shade plugin that I could find, I got
> > > this
> > > > > from
> > > > > looking at the CXF build and the Shade plugin source code.
> > > > >
> > > > >
> > > > > > - We have two different servlet-api JARs, should we pick one?
> > > > >
> > > > >
> > > > > Fixed. The 6.0.10 one was coming from the http-tomcat module so
> i've
> > > > added
> > > > > exclusions in that pom.xml.
> > > > >
> > > > > - Could we have, in the bin distro, a tuscany-sca-src.jarcontaining
> > > all
> > > > > > the source code for the classes in tuscany-sca.jar?
> > > > >
> > > > >
> > > > > Thats a good idea, I'm not sure how though. The tuscany-sca.jar is
> > > built
> > > > > from all the <dependency> elements listed in the
> > > > > distribution/bundle/pom.xml, I could make a src jar by just
> zipping
> > up
> > > > > everything in sca/modules but it may end up including more than is
> > in
> > > > the
> > > > > tuscany-sca.jar. Anyone have any better ideas on how to do this?
> > > > >
> > > > > - How about renaming tuscany-sca.jar to tuscany-sca-all.jar, or
> any
> > > name
> > > > > > indicating that it's all the tuscany code?
> > > > >
> > > > >
> > > > > OK, done.
> > > > >
> > > > > - The NOTICE will have to be updated as it contains obsolete
> > > > dependencies.
> > > > >
> > > > >
> > > > > Yep. Over the next days I'll trawl through all the license and
> > notice
> > > > > files
> > > > > to make sure they're correct.
> > > > >
> > > > > - I think it would be great to have Ant build scripts for some of
> > the
> > > > > > samples, as not everybody is using Maven.
> > > > >
> > > > >
> > > > > Me too, I'll try to get one going today. Should we have all the
> > > samples
> > > > > have
> > > > > both maven and Ant build scripts, or just Ant, or some samples
> have
> > > Ant
> > > > > and
> > > > > others have Maven?
> > > > >
> > > > > - Pre-built sample JARs would be great too, but not as important
> if
> > we
> > > > > > have a simple Ant build for the samples.
> > > > >
> > > > >
> > > > > There are pre-built sample jars in the sample target directory,
> eg,
> > > > > samples\calculator\target\tuscany-
> > > > > sample-calculator-1.0-incubating-SNAPSHOT.jar
> > > > >
> > > > > I've updated the distribution build scripts with the above changes
> > > now.
> > > > >
> > > > > ...ant
> > > > >
> > > > Hi I just this minute took a fresh update of sca to make ant scripts
> > for
> > > > the
> > > > samples. I have some questions...
> > > >
> > > > - why does tuscany-sca-manifest.jar not have a version number?
> > > > - What is intention of tuscany-sca-all.... I need a classpath with
> all
> > > > tuscany jars on. Currently its in tuscany-sca-manifest but it
> doesn't
> > > pick
> > > > up the dependencies in the modules directory as they are in
> ../modules
> > >
> > >
> > > The idea is that tuscany-sca-manifest.jar is an easy way for users to
> be
> > > able to add tuscany-sca and all the dependencies to their classpath
> when
> > > they have the binary distribution. It only works when its in the same
> > > directory as all the other jars so its not distributed out side of the
> > > binary distro so i don't think it needs "-incubating-" in the name,
> and
> > > because its not distributed separately i left off a version number,
> not
> > > sure
> > > if thats good or not but it does make the name nice and short.
> >
> >
> > Ok, fair point.
> >
> > The tuscany-sca-all-1.0-incubating-SNAPSHOT.jar is made from combining
> all
> > > the tuscany-sca modules into a single jar. It would get published to
> the
> > > maven repository so needs "-incubating-" and a version number in the
> > name.
> > > The idea for this jar is that while its good to have lots of
> individual
> > > modules for Tuscany developers as that prevents code tangles but that
> > > actually makes things harder for users as they have dozens of jars to
> > > worry
> > > about. This is a first attempt at the -all- jar which just incudes
> > > _everything_, we may end up wanting different versions for different
> > > environments.
> >
> >
> > Sounds like a good idea to me. A question about the state of the build
> > today (I appreciate this is just a point in time so not giving you a
> hard
> > time). When I run the distribution build I get a bin zip where
> >
> > 1. tuscany-sca-all-1.0-incubation-SNAPSHOT.jar is in the lib dir
> > 2. It doesn't appear to have any useful content (maybe I'm looking at it
> > the
> > wrong way)
> > 3. tuscany-sca-manifest.jar has all of the tuscany libs referenced in
> its
> > manifest but of course they are not in the lib dir so I can;t make use
> of
> > that list
> >
> > Happy to help trying to make this work but I don't know whether its a
> > product of my environment or whether this just isn't done yet.
>
>
> This seems like a bug. I've posted the binary distro I built this morning
> at
> http://people.apache.org/~antelder/tuscany/latest/, that doesn't look like
> the one you get? The all jar is created by the distribution/bundle module,
> i've posted the console log from me building that at
> http://rafb.net/p/3zqmcK41.html, how does that compare to when you do
> that?
>
> ...ant
>
--
Paulo Henrique Trecenti
Re: Next SCA release distributions
Posted by ant elder <an...@gmail.com>.
On 5/2/07, Simon Laws <si...@googlemail.com> wrote:
>
> On 5/2/07, ant elder <an...@gmail.com> wrote:
> >
> > On 5/2/07, Simon Laws <si...@googlemail.com> wrote:
> > >
> > > On 4/30/07, ant elder <an...@gmail.com> wrote:
> > > >
> > > > Excellent thanks, thats type type feedback I was looking for!
> Comments
> > > in
> > > > line...
> > > >
> > > > On 4/30/07, Jean-Sebastien Delfino <js...@apache.org> wrote:
> > > >
> > > > <snip/>
> > > >
> > > > I have a few questions and suggestions.
> > > > > - tuscany-sca.jar contains .svn directories, I guess they should
> be
> > > > > removed from the JAR.
> > > >
> > > >
> > > > I can't see these, i could just be blind or maybe its something
> > > different
> > > > about our environments could you give an example of what the file
> > names
> > > > are?
> > > >
> > > > - Also 2 empty xsds at the root of the JAR and com.example packages,
> > > > > they must be coming from one of the examples?
> > > >
> > > >
> > > > The com.example.* files are coming from the databinding-jaxb and
> > > > databinding-sdo modules, we need to fix those modules but I'm not
> sure
> > > > how.
> > > > It looks like the jaxb and sdo plugins need to some way to say
> they're
> > > > test
> > > > resources. Any one know how to fix this?
> > > >
> > > > I can't see the 2 empty xsds, something different about our
> > environments
> > > > again?
> > > >
> > > > - I guess we're going to rename this to sca-1.0-beta1-incubating?
> > > >
> > > >
> > > > Yes, the name should be being picked up from the pom, but i'll test
> it
> > > > does
> > > > change. (Using the current format the name would be
> > 1.0-incubating-beta1
> > > ,
> > > > do
> > > > we really want 1.0-beta1-incubating?)
> > > >
> > > > - Like you said above, we'll have to include the javadoc for our
> SPIs.
> > > >
> > > >
> > > > Yes, I guess I can add that in now even though the SPIs aren't done
> by
> > > > just
> > > > including the tuscany-core-spi module javadoc. Is javadoc for just
> > these
> > > > two
> > > > modules enough (sca-api and core-spi). I've added this now, are
> there
> > > > other
> > > > modules we want javadoc for?
> > > >
> > > > - How did you produce the single
> META-INF/services/...ModuleActivator
> > > > > file? is it generated?
> > > >
> > > >
> > > > This is done in the java/sca/distribution/bundle project using the
> > Maven
> > > > Shade plugin, see in the pom.xml the shade config where a Shade
> > > > AppendingTransformer is used to merge all the ModuleActivator files
> > into
> > > > one. No doc at all about the Shade plugin that I could find, I got
> > this
> > > > from
> > > > looking at the CXF build and the Shade plugin source code.
> > > >
> > > >
> > > > > - We have two different servlet-api JARs, should we pick one?
> > > >
> > > >
> > > > Fixed. The 6.0.10 one was coming from the http-tomcat module so i've
> > > added
> > > > exclusions in that pom.xml.
> > > >
> > > > - Could we have, in the bin distro, a tuscany-sca-src.jar containing
> > all
> > > > > the source code for the classes in tuscany-sca.jar?
> > > >
> > > >
> > > > Thats a good idea, I'm not sure how though. The tuscany-sca.jar is
> > built
> > > > from all the <dependency> elements listed in the
> > > > distribution/bundle/pom.xml, I could make a src jar by just zipping
> up
> > > > everything in sca/modules but it may end up including more than is
> in
> > > the
> > > > tuscany-sca.jar. Anyone have any better ideas on how to do this?
> > > >
> > > > - How about renaming tuscany-sca.jar to tuscany-sca-all.jar, or any
> > name
> > > > > indicating that it's all the tuscany code?
> > > >
> > > >
> > > > OK, done.
> > > >
> > > > - The NOTICE will have to be updated as it contains obsolete
> > > dependencies.
> > > >
> > > >
> > > > Yep. Over the next days I'll trawl through all the license and
> notice
> > > > files
> > > > to make sure they're correct.
> > > >
> > > > - I think it would be great to have Ant build scripts for some of
> the
> > > > > samples, as not everybody is using Maven.
> > > >
> > > >
> > > > Me too, I'll try to get one going today. Should we have all the
> > samples
> > > > have
> > > > both maven and Ant build scripts, or just Ant, or some samples have
> > Ant
> > > > and
> > > > others have Maven?
> > > >
> > > > - Pre-built sample JARs would be great too, but not as important if
> we
> > > > > have a simple Ant build for the samples.
> > > >
> > > >
> > > > There are pre-built sample jars in the sample target directory, eg,
> > > > samples\calculator\target\tuscany-
> > > > sample-calculator-1.0-incubating-SNAPSHOT.jar
> > > >
> > > > I've updated the distribution build scripts with the above changes
> > now.
> > > >
> > > > ...ant
> > > >
> > > Hi I just this minute took a fresh update of sca to make ant scripts
> for
> > > the
> > > samples. I have some questions...
> > >
> > > - why does tuscany-sca-manifest.jar not have a version number?
> > > - What is intention of tuscany-sca-all.... I need a classpath with all
> > > tuscany jars on. Currently its in tuscany-sca-manifest but it doesn't
> > pick
> > > up the dependencies in the modules directory as they are in ../modules
> >
> >
> > The idea is that tuscany-sca-manifest.jar is an easy way for users to be
> > able to add tuscany-sca and all the dependencies to their classpath when
> > they have the binary distribution. It only works when its in the same
> > directory as all the other jars so its not distributed out side of the
> > binary distro so i don't think it needs "-incubating-" in the name, and
> > because its not distributed separately i left off a version number, not
> > sure
> > if thats good or not but it does make the name nice and short.
>
>
> Ok, fair point.
>
> The tuscany-sca-all-1.0-incubating-SNAPSHOT.jar is made from combining all
> > the tuscany-sca modules into a single jar. It would get published to the
> > maven repository so needs "-incubating-" and a version number in the
> name.
> > The idea for this jar is that while its good to have lots of individual
> > modules for Tuscany developers as that prevents code tangles but that
> > actually makes things harder for users as they have dozens of jars to
> > worry
> > about. This is a first attempt at the -all- jar which just incudes
> > _everything_, we may end up wanting different versions for different
> > environments.
>
>
> Sounds like a good idea to me. A question about the state of the build
> today (I appreciate this is just a point in time so not giving you a hard
> time). When I run the distribution build I get a bin zip where
>
> 1. tuscany-sca-all-1.0-incubation-SNAPSHOT.jar is in the lib dir
> 2. It doesn't appear to have any useful content (maybe I'm looking at it
> the
> wrong way)
> 3. tuscany-sca-manifest.jar has all of the tuscany libs referenced in its
> manifest but of course they are not in the lib dir so I can;t make use of
> that list
>
> Happy to help trying to make this work but I don't know whether its a
> product of my environment or whether this just isn't done yet.
This seems like a bug. I've posted the binary distro I built this morning at
http://people.apache.org/~antelder/tuscany/latest/, that doesn't look like
the one you get? The all jar is created by the distribution/bundle module,
i've posted the console log from me building that at
http://rafb.net/p/3zqmcK41.html, how does that compare to when you do that?
...ant
Re: Next SCA release distributions
Posted by Simon Laws <si...@googlemail.com>.
On 5/2/07, ant elder <an...@gmail.com> wrote:
>
> On 5/2/07, Simon Laws <si...@googlemail.com> wrote:
> >
> > On 4/30/07, ant elder <an...@gmail.com> wrote:
> > >
> > > Excellent thanks, thats type type feedback I was looking for! Comments
> > in
> > > line...
> > >
> > > On 4/30/07, Jean-Sebastien Delfino <js...@apache.org> wrote:
> > >
> > > <snip/>
> > >
> > > I have a few questions and suggestions.
> > > > - tuscany-sca.jar contains .svn directories, I guess they should be
> > > > removed from the JAR.
> > >
> > >
> > > I can't see these, i could just be blind or maybe its something
> > different
> > > about our environments could you give an example of what the file
> names
> > > are?
> > >
> > > - Also 2 empty xsds at the root of the JAR and com.example packages,
> > > > they must be coming from one of the examples?
> > >
> > >
> > > The com.example.* files are coming from the databinding-jaxb and
> > > databinding-sdo modules, we need to fix those modules but I'm not sure
> > > how.
> > > It looks like the jaxb and sdo plugins need to some way to say they're
> > > test
> > > resources. Any one know how to fix this?
> > >
> > > I can't see the 2 empty xsds, something different about our
> environments
> > > again?
> > >
> > > - I guess we're going to rename this to sca-1.0-beta1-incubating?
> > >
> > >
> > > Yes, the name should be being picked up from the pom, but i'll test it
> > > does
> > > change. (Using the current format the name would be
> 1.0-incubating-beta1
> > ,
> > > do
> > > we really want 1.0-beta1-incubating?)
> > >
> > > - Like you said above, we'll have to include the javadoc for our SPIs.
> > >
> > >
> > > Yes, I guess I can add that in now even though the SPIs aren't done by
> > > just
> > > including the tuscany-core-spi module javadoc. Is javadoc for just
> these
> > > two
> > > modules enough (sca-api and core-spi). I've added this now, are there
> > > other
> > > modules we want javadoc for?
> > >
> > > - How did you produce the single META-INF/services/...ModuleActivator
> > > > file? is it generated?
> > >
> > >
> > > This is done in the java/sca/distribution/bundle project using the
> Maven
> > > Shade plugin, see in the pom.xml the shade config where a Shade
> > > AppendingTransformer is used to merge all the ModuleActivator files
> into
> > > one. No doc at all about the Shade plugin that I could find, I got
> this
> > > from
> > > looking at the CXF build and the Shade plugin source code.
> > >
> > >
> > > > - We have two different servlet-api JARs, should we pick one?
> > >
> > >
> > > Fixed. The 6.0.10 one was coming from the http-tomcat module so i've
> > added
> > > exclusions in that pom.xml.
> > >
> > > - Could we have, in the bin distro, a tuscany-sca-src.jar containing
> all
> > > > the source code for the classes in tuscany-sca.jar?
> > >
> > >
> > > Thats a good idea, I'm not sure how though. The tuscany-sca.jar is
> built
> > > from all the <dependency> elements listed in the
> > > distribution/bundle/pom.xml, I could make a src jar by just zipping up
> > > everything in sca/modules but it may end up including more than is in
> > the
> > > tuscany-sca.jar. Anyone have any better ideas on how to do this?
> > >
> > > - How about renaming tuscany-sca.jar to tuscany-sca-all.jar, or any
> name
> > > > indicating that it's all the tuscany code?
> > >
> > >
> > > OK, done.
> > >
> > > - The NOTICE will have to be updated as it contains obsolete
> > dependencies.
> > >
> > >
> > > Yep. Over the next days I'll trawl through all the license and notice
> > > files
> > > to make sure they're correct.
> > >
> > > - I think it would be great to have Ant build scripts for some of the
> > > > samples, as not everybody is using Maven.
> > >
> > >
> > > Me too, I'll try to get one going today. Should we have all the
> samples
> > > have
> > > both maven and Ant build scripts, or just Ant, or some samples have
> Ant
> > > and
> > > others have Maven?
> > >
> > > - Pre-built sample JARs would be great too, but not as important if we
> > > > have a simple Ant build for the samples.
> > >
> > >
> > > There are pre-built sample jars in the sample target directory, eg,
> > > samples\calculator\target\tuscany-
> > > sample-calculator-1.0-incubating-SNAPSHOT.jar
> > >
> > > I've updated the distribution build scripts with the above changes
> now.
> > >
> > > ...ant
> > >
> > Hi I just this minute took a fresh update of sca to make ant scripts for
> > the
> > samples. I have some questions...
> >
> > - why does tuscany-sca-manifest.jar not have a version number?
> > - What is intention of tuscany-sca-all.... I need a classpath with all
> > tuscany jars on. Currently its in tuscany-sca-manifest but it doesn't
> pick
> > up the dependencies in the modules directory as they are in ../modules
>
>
> The idea is that tuscany-sca-manifest.jar is an easy way for users to be
> able to add tuscany-sca and all the dependencies to their classpath when
> they have the binary distribution. It only works when its in the same
> directory as all the other jars so its not distributed out side of the
> binary distro so i don't think it needs "-incubating-" in the name, and
> because its not distributed separately i left off a version number, not
> sure
> if thats good or not but it does make the name nice and short.
Ok, fair point.
The tuscany-sca-all-1.0-incubating-SNAPSHOT.jar is made from combining all
> the tuscany-sca modules into a single jar. It would get published to the
> maven repository so needs "-incubating-" and a version number in the name.
> The idea for this jar is that while its good to have lots of individual
> modules for Tuscany developers as that prevents code tangles but that
> actually makes things harder for users as they have dozens of jars to
> worry
> about. This is a first attempt at the -all- jar which just incudes
> _everything_, we may end up wanting different versions for different
> environments.
Sounds like a good idea to me. A question about the state of the build
today (I appreciate this is just a point in time so not giving you a hard
time). When I run the distribution build I get a bin zip where
1. tuscany-sca-all-1.0-incubation-SNAPSHOT.jar is in the lib dir
2. It doesn't appear to have any useful content (maybe I'm looking at it the
wrong way)
3. tuscany-sca-manifest.jar has all of the tuscany libs referenced in its
manifest but of course they are not in the lib dir so I can;t make use of
that list
Happy to help trying to make this work but I don't know whether its a
product of my environment or whether this just isn't done yet.
This is just a strawman distro, so there's going to be mistakes and better
> ways of doing things so please do suggest improvements :) There's a couple
> of threads discussing the pros and cons of various approaches at [1] and
> [2].
>
> - tuscany-rmi? Should this be a binding
>
>
> Yes, would be better as tuscany-binding-rmi.
>
> I've checked in a build.xml to the calculator sample that I'm playing with
> > (I took it from M2). But thinking about this if we go with ant builds
> for
> > this release it would be good if they work for the binary release and
> the
> > src release. Even if its just the "run" target. So how to we construct
> the
> > classpath to make this work. I'm just building th src distro to see if
> it
> > creats a lib dir but we could do with something like tuscan-sca-manifest
> > to
> > keep the ant script simple.
>
>
> I think the Ant scripts should definitely work in the binary distro by
> using
> the jars in the lib directory, but thats not going to work in the src
> distro. Maybe we could just say the Ant scripts don't work in the src
> distro, and there you have to use mvn?
Mmm. Ok we could. I'll let this one sink in a bit and play with it to see
if it make sense. I would like to have a consistent way of running the
samples regardless of how they are build so that's why I'm not sure.
As I'm looking at the calculator sample I'm updating the readme.html. I plan
> > to reinstate sca/doc/css if no one has any objections.
>
>
> Or we could go back to simple text files for the readme's?
Ok, can do. I guess it makes them more generally accessible. I can change to
readme.txt
Regards
> >
> > Simon
> >
>
>
> ...ant
>
> [1]
>
> http://mail-archives.apache.org/mod_mbox/incubator-cxf-user/200703.mbox/%3cC686FD10-296D-40BD-804B-717878947724@formicary.net%3e
> [2]
>
> http://mail-archives.apache.org/mod_mbox/incubator-cxf-dev/200610.mbox/%3c2CAF7ABD-1AA9-4755-B45F-1D475682710B@iona.com%3e
>
Re: Next SCA release distributions
Posted by ant elder <an...@gmail.com>.
On 5/2/07, Simon Laws <si...@googlemail.com> wrote:
>
> On 4/30/07, ant elder <an...@gmail.com> wrote:
> >
> > Excellent thanks, thats type type feedback I was looking for! Comments
> in
> > line...
> >
> > On 4/30/07, Jean-Sebastien Delfino <js...@apache.org> wrote:
> >
> > <snip/>
> >
> > I have a few questions and suggestions.
> > > - tuscany-sca.jar contains .svn directories, I guess they should be
> > > removed from the JAR.
> >
> >
> > I can't see these, i could just be blind or maybe its something
> different
> > about our environments could you give an example of what the file names
> > are?
> >
> > - Also 2 empty xsds at the root of the JAR and com.example packages,
> > > they must be coming from one of the examples?
> >
> >
> > The com.example.* files are coming from the databinding-jaxb and
> > databinding-sdo modules, we need to fix those modules but I'm not sure
> > how.
> > It looks like the jaxb and sdo plugins need to some way to say they're
> > test
> > resources. Any one know how to fix this?
> >
> > I can't see the 2 empty xsds, something different about our environments
> > again?
> >
> > - I guess we're going to rename this to sca-1.0-beta1-incubating?
> >
> >
> > Yes, the name should be being picked up from the pom, but i'll test it
> > does
> > change. (Using the current format the name would be 1.0-incubating-beta1
> ,
> > do
> > we really want 1.0-beta1-incubating?)
> >
> > - Like you said above, we'll have to include the javadoc for our SPIs.
> >
> >
> > Yes, I guess I can add that in now even though the SPIs aren't done by
> > just
> > including the tuscany-core-spi module javadoc. Is javadoc for just these
> > two
> > modules enough (sca-api and core-spi). I've added this now, are there
> > other
> > modules we want javadoc for?
> >
> > - How did you produce the single META-INF/services/...ModuleActivator
> > > file? is it generated?
> >
> >
> > This is done in the java/sca/distribution/bundle project using the Maven
> > Shade plugin, see in the pom.xml the shade config where a Shade
> > AppendingTransformer is used to merge all the ModuleActivator files into
> > one. No doc at all about the Shade plugin that I could find, I got this
> > from
> > looking at the CXF build and the Shade plugin source code.
> >
> >
> > > - We have two different servlet-api JARs, should we pick one?
> >
> >
> > Fixed. The 6.0.10 one was coming from the http-tomcat module so i've
> added
> > exclusions in that pom.xml.
> >
> > - Could we have, in the bin distro, a tuscany-sca-src.jar containing all
> > > the source code for the classes in tuscany-sca.jar?
> >
> >
> > Thats a good idea, I'm not sure how though. The tuscany-sca.jar is built
> > from all the <dependency> elements listed in the
> > distribution/bundle/pom.xml, I could make a src jar by just zipping up
> > everything in sca/modules but it may end up including more than is in
> the
> > tuscany-sca.jar. Anyone have any better ideas on how to do this?
> >
> > - How about renaming tuscany-sca.jar to tuscany-sca-all.jar, or any name
> > > indicating that it's all the tuscany code?
> >
> >
> > OK, done.
> >
> > - The NOTICE will have to be updated as it contains obsolete
> dependencies.
> >
> >
> > Yep. Over the next days I'll trawl through all the license and notice
> > files
> > to make sure they're correct.
> >
> > - I think it would be great to have Ant build scripts for some of the
> > > samples, as not everybody is using Maven.
> >
> >
> > Me too, I'll try to get one going today. Should we have all the samples
> > have
> > both maven and Ant build scripts, or just Ant, or some samples have Ant
> > and
> > others have Maven?
> >
> > - Pre-built sample JARs would be great too, but not as important if we
> > > have a simple Ant build for the samples.
> >
> >
> > There are pre-built sample jars in the sample target directory, eg,
> > samples\calculator\target\tuscany-
> > sample-calculator-1.0-incubating-SNAPSHOT.jar
> >
> > I've updated the distribution build scripts with the above changes now.
> >
> > ...ant
> >
> Hi I just this minute took a fresh update of sca to make ant scripts for
> the
> samples. I have some questions...
>
> - why does tuscany-sca-manifest.jar not have a version number?
> - What is intention of tuscany-sca-all.... I need a classpath with all
> tuscany jars on. Currently its in tuscany-sca-manifest but it doesn't pick
> up the dependencies in the modules directory as they are in ../modules
The idea is that tuscany-sca-manifest.jar is an easy way for users to be
able to add tuscany-sca and all the dependencies to their classpath when
they have the binary distribution. It only works when its in the same
directory as all the other jars so its not distributed out side of the
binary distro so i don't think it needs "-incubating-" in the name, and
because its not distributed separately i left off a version number, not sure
if thats good or not but it does make the name nice and short.
The tuscany-sca-all-1.0-incubating-SNAPSHOT.jar is made from combining all
the tuscany-sca modules into a single jar. It would get published to the
maven repository so needs "-incubating-" and a version number in the name.
The idea for this jar is that while its good to have lots of individual
modules for Tuscany developers as that prevents code tangles but that
actually makes things harder for users as they have dozens of jars to worry
about. This is a first attempt at the -all- jar which just incudes
_everything_, we may end up wanting different versions for different
environments.
This is just a strawman distro, so there's going to be mistakes and better
ways of doing things so please do suggest improvements :) There's a couple
of threads discussing the pros and cons of various approaches at [1] and
[2].
- tuscany-rmi? Should this be a binding
Yes, would be better as tuscany-binding-rmi.
I've checked in a build.xml to the calculator sample that I'm playing with
> (I took it from M2). But thinking about this if we go with ant builds for
> this release it would be good if they work for the binary release and the
> src release. Even if its just the "run" target. So how to we construct the
> classpath to make this work. I'm just building th src distro to see if it
> creats a lib dir but we could do with something like tuscan-sca-manifest
> to
> keep the ant script simple.
I think the Ant scripts should definitely work in the binary distro by using
the jars in the lib directory, but thats not going to work in the src
distro. Maybe we could just say the Ant scripts don't work in the src
distro, and there you have to use mvn?
As I'm looking at the calculator sample I'm updating the readme.html. I plan
> to reinstate sca/doc/css if no one has any objections.
Or we could go back to simple text files for the readme's?
Regards
>
> Simon
>
...ant
[1]
http://mail-archives.apache.org/mod_mbox/incubator-cxf-user/200703.mbox/%3cC686FD10-296D-40BD-804B-717878947724@formicary.net%3e
[2]
http://mail-archives.apache.org/mod_mbox/incubator-cxf-dev/200610.mbox/%3c2CAF7ABD-1AA9-4755-B45F-1D475682710B@iona.com%3e
Re: Next SCA release distributions
Posted by Simon Laws <si...@googlemail.com>.
On 4/30/07, ant elder <an...@gmail.com> wrote:
>
> Excellent thanks, thats type type feedback I was looking for! Comments in
> line...
>
> On 4/30/07, Jean-Sebastien Delfino <js...@apache.org> wrote:
>
> <snip/>
>
> I have a few questions and suggestions.
> > - tuscany-sca.jar contains .svn directories, I guess they should be
> > removed from the JAR.
>
>
> I can't see these, i could just be blind or maybe its something different
> about our environments could you give an example of what the file names
> are?
>
> - Also 2 empty xsds at the root of the JAR and com.example packages,
> > they must be coming from one of the examples?
>
>
> The com.example.* files are coming from the databinding-jaxb and
> databinding-sdo modules, we need to fix those modules but I'm not sure
> how.
> It looks like the jaxb and sdo plugins need to some way to say they're
> test
> resources. Any one know how to fix this?
>
> I can't see the 2 empty xsds, something different about our environments
> again?
>
> - I guess we're going to rename this to sca-1.0-beta1-incubating?
>
>
> Yes, the name should be being picked up from the pom, but i'll test it
> does
> change. (Using the current format the name would be 1.0-incubating-beta1,
> do
> we really want 1.0-beta1-incubating?)
>
> - Like you said above, we'll have to include the javadoc for our SPIs.
>
>
> Yes, I guess I can add that in now even though the SPIs aren't done by
> just
> including the tuscany-core-spi module javadoc. Is javadoc for just these
> two
> modules enough (sca-api and core-spi). I've added this now, are there
> other
> modules we want javadoc for?
>
> - How did you produce the single META-INF/services/...ModuleActivator
> > file? is it generated?
>
>
> This is done in the java/sca/distribution/bundle project using the Maven
> Shade plugin, see in the pom.xml the shade config where a Shade
> AppendingTransformer is used to merge all the ModuleActivator files into
> one. No doc at all about the Shade plugin that I could find, I got this
> from
> looking at the CXF build and the Shade plugin source code.
>
>
> > - We have two different servlet-api JARs, should we pick one?
>
>
> Fixed. The 6.0.10 one was coming from the http-tomcat module so i've added
> exclusions in that pom.xml.
>
> - Could we have, in the bin distro, a tuscany-sca-src.jar containing all
> > the source code for the classes in tuscany-sca.jar?
>
>
> Thats a good idea, I'm not sure how though. The tuscany-sca.jar is built
> from all the <dependency> elements listed in the
> distribution/bundle/pom.xml, I could make a src jar by just zipping up
> everything in sca/modules but it may end up including more than is in the
> tuscany-sca.jar. Anyone have any better ideas on how to do this?
>
> - How about renaming tuscany-sca.jar to tuscany-sca-all.jar, or any name
> > indicating that it's all the tuscany code?
>
>
> OK, done.
>
> - The NOTICE will have to be updated as it contains obsolete dependencies.
>
>
> Yep. Over the next days I'll trawl through all the license and notice
> files
> to make sure they're correct.
>
> - I think it would be great to have Ant build scripts for some of the
> > samples, as not everybody is using Maven.
>
>
> Me too, I'll try to get one going today. Should we have all the samples
> have
> both maven and Ant build scripts, or just Ant, or some samples have Ant
> and
> others have Maven?
>
> - Pre-built sample JARs would be great too, but not as important if we
> > have a simple Ant build for the samples.
>
>
> There are pre-built sample jars in the sample target directory, eg,
> samples\calculator\target\tuscany-
> sample-calculator-1.0-incubating-SNAPSHOT.jar
>
> I've updated the distribution build scripts with the above changes now.
>
> ...ant
>
Hi I just this minute took a fresh update of sca to make ant scripts for the
samples. I have some questions...
- why does tuscany-sca-manifest.jar not have a version number?
- What is intention of tuscany-sca-all.... I need a classpath with all
tuscany jars on. Currently its in tuscany-sca-manifest but it doesn't pick
up the dependencies in the modules directory as they are in ../modules
- tuscany-rmi? Should this be a binding
I've checked in a build.xml to the calculator sample that I'm playing with
(I took it from M2). But thinking about this if we go with ant builds for
this release it would be good if they work for the binary release and the
src release. Even if its just the "run" target. So how to we construct the
classpath to make this work. I'm just building th src distro to see if it
creats a lib dir but we could do with something like tuscan-sca-manifest to
keep the ant script simple.
As I'm looking at the calculator sample I'm updating the readme.html. I plan
to reinstate sca/doc/css if no one has any objections.
Regards
Simon
Re: Next SCA release distributions
Posted by ant elder <an...@gmail.com>.
Excellent thanks, thats type type feedback I was looking for! Comments in
line...
On 4/30/07, Jean-Sebastien Delfino <js...@apache.org> wrote:
<snip/>
I have a few questions and suggestions.
> - tuscany-sca.jar contains .svn directories, I guess they should be
> removed from the JAR.
I can't see these, i could just be blind or maybe its something different
about our environments could you give an example of what the file names are?
- Also 2 empty xsds at the root of the JAR and com.example packages,
> they must be coming from one of the examples?
The com.example.* files are coming from the databinding-jaxb and
databinding-sdo modules, we need to fix those modules but I'm not sure how.
It looks like the jaxb and sdo plugins need to some way to say they're test
resources. Any one know how to fix this?
I can't see the 2 empty xsds, something different about our environments
again?
- I guess we're going to rename this to sca-1.0-beta1-incubating?
Yes, the name should be being picked up from the pom, but i'll test it does
change. (Using the current format the name would be 1.0-incubating-beta1, do
we really want 1.0-beta1-incubating?)
- Like you said above, we'll have to include the javadoc for our SPIs.
Yes, I guess I can add that in now even though the SPIs aren't done by just
including the tuscany-core-spi module javadoc. Is javadoc for just these two
modules enough (sca-api and core-spi). I've added this now, are there other
modules we want javadoc for?
- How did you produce the single META-INF/services/...ModuleActivator
> file? is it generated?
This is done in the java/sca/distribution/bundle project using the Maven
Shade plugin, see in the pom.xml the shade config where a Shade
AppendingTransformer is used to merge all the ModuleActivator files into
one. No doc at all about the Shade plugin that I could find, I got this from
looking at the CXF build and the Shade plugin source code.
> - We have two different servlet-api JARs, should we pick one?
Fixed. The 6.0.10 one was coming from the http-tomcat module so i've added
exclusions in that pom.xml.
- Could we have, in the bin distro, a tuscany-sca-src.jar containing all
> the source code for the classes in tuscany-sca.jar?
Thats a good idea, I'm not sure how though. The tuscany-sca.jar is built
from all the <dependency> elements listed in the
distribution/bundle/pom.xml, I could make a src jar by just zipping up
everything in sca/modules but it may end up including more than is in the
tuscany-sca.jar. Anyone have any better ideas on how to do this?
- How about renaming tuscany-sca.jar to tuscany-sca-all.jar, or any name
> indicating that it's all the tuscany code?
OK, done.
- The NOTICE will have to be updated as it contains obsolete dependencies.
Yep. Over the next days I'll trawl through all the license and notice files
to make sure they're correct.
- I think it would be great to have Ant build scripts for some of the
> samples, as not everybody is using Maven.
Me too, I'll try to get one going today. Should we have all the samples have
both maven and Ant build scripts, or just Ant, or some samples have Ant and
others have Maven?
- Pre-built sample JARs would be great too, but not as important if we
> have a simple Ant build for the samples.
There are pre-built sample jars in the sample target directory, eg,
samples\calculator\target\tuscany-
sample-calculator-1.0-incubating-SNAPSHOT.jar
I've updated the distribution build scripts with the above changes now.
...ant
Re: Next SCA release distributions
Posted by Jean-Sebastien Delfino <js...@apache.org>.
ant elder wrote:
> On 4/29/07, ant elder <an...@gmail.com> 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: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
Re: Next SCA release distributions
Posted by ant elder <an...@gmail.com>.
On 4/29/07, ant elder <an...@gmail.com> 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
Re: Next SCA release distributions
Posted by ant elder <an...@gmail.com>.
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/%3c462F873A.8050708@apache.org%3e
...ant
On 4/29/07, 王洪伟 <da...@gmail.com> 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 <an...@gmail.com>:
> >
> > 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
> >
>
Re: Next SCA release distributions
Posted by 王洪伟 <da...@gmail.com>.
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 <an...@gmail.com>:
>
> 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.
>
> ...ant
>