ant elder wrote:
On Mon, Apr 11, 2011 at 1:02 PM, Simon Nash <[email protected]> wrote:
+1, the shell is good for people learning SCA, and ant scripts are good
for showing how to embed Tuscany. A mixture of both styles in the samples
is a good approach.
Why are Ant scripts especially good for showing how to embed Tuscany?
Looking at the 2.x store one [1] or the 1.x calculator one [2] they
use the single manifest jar approach which doesn't make it
particularly clear what dependencies are required. A Maven pom.xml and
things like "mvn dependency:tree" seem more clear and useful. I'm not
saying there shouldn't be Ant builds if anyone wants to add them, but
i'm not sure that any one has come up with a particularly good
approach for them yet IMHO.
These scripts show the exact java command needed to launch the sample,
including a static classpath containing all the necessary runtime
dependencies for the sample. This is the essential information that
an embedder needs to get started with Tuscany.
It might be possible to optimize the classpath slightly by removing some
runtime code that isn't needed by a specific sample. If we could provide
some sample ant scripts that do this (for example, using base and extension
jars instead of tuscany-sca-manifest), that would be useful as well.
Simon
...ant
[1]
https://svn.apache.org/repos/asf/tuscany/sca-java-2.x/trunk/samples/applications/store/build.xml
[2]
https://svn.apache.org/repos/asf/tuscany/sca-java-1.x/trunk/samples/calculator/build.xml
