ant elder wrote:
On Thu, Feb 10, 2011 at 10:36 AM, Florian Moga <moga....@gmail.com> wrote:
I'm not keen into having an ant build file in every sample. If someone wants
to use ant, shouldn't they download all dependencies manually? Won't they
use maven for that task anyway? What about ivy?
I've been thinking the same thing lately, especially now that you
pointed out that we can do "mvn ant:ant" to have Ant scripts
automatically generated. Instead of Ant builds for each sample there
could just be some doc in the top level samples folder or README that
describes how to use "mvn ant:ant".
The build scripts generated with mvn ant:ant download all the
dependencies from the Maven repositories, that does mean that not much
would be actually using all the jars from the Tuscany binary
distribution so we might want to consider what all thats really for.
...ant
Actually I would wonder what is the point of using maven to generate
an ant script that does exactly the same as the maven build.
In 1.x the ant scripts were provided as an alternative to maven that
use local artifacts from the binary distro instead of depending on
remote repositories. Another purpose was to make it very clear and
explicit what steps are involved "under the covers" to build and run
Tuscany applications. This information is useful to people who want
to develop solutions that embed Tuscany.
Simon
