Hi, Simon.
The ant script looks good to me.
I would suggest that we document the web app packaging scheme and runtime
classloading behavior. I already have some related information collected at
http://wiki.apache.org/ws/Tuscany/TuscanyJava/WebApp. It will help the users
understand the rationale and potentially use manual steps or alternative
approach as illustrated by your ant script.
IMHO, Ant and Maven are two build tools. Making Ant to deal with remote and
transitive dependencies will not necessarily lower the bar for users. The
whole purpose of this excercise is that we tell users the story and give
them choices to either assemble the web application manually by copying a
bunch of jars to the right location or automatically by using maven, ant or
some other tools.
BTW, would it be acceptable to download individual jars from the maven repo
using HTTP as we don't have an all-in-one binary distro?
Thanks,
Raymond
----- Original Message -----
From: "Simon Nash" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Tuesday, November 14, 2006 9:10 AM
Subject: Updated ant scripts attached to TUSCANY-906
I have attached updated ant scripts for calculator and helloworldws
to TUSCANY-906. Following Raymond's suggestion, they eliminate all
the <copy> tasks. This makes them less "scary" than the previous
versions, and makes it easier to see how to build a Tuscany standalone
application or a Tuscany webapp. Any further suggestions for
improvement are very welcome.
At present these scripts still use standard ant tasks and so require
the 2 Tuscany webapp jars to be available locally. I'm now going to
start working on a solution that can handle remote dependencies.
Simon
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
