tuscany-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ant elder" <ant.el...@gmail.com>
Subject Re: R1.1 - Sample/demo ant builds
Date Wed, 02 Jan 2008 09:23:32 GMT
On Jan 2, 2008 8:58 AM, Simon Laws <simonslaws@googlemail.com> wrote:

> For http://issues.apache.org/jira/browse/TUSCANY-1608 I've put in a
> change,
> based on the ant generator plugin, to bring some automation to the process
> of building the ant files for the samples and demos. For any sample or
> demo
> that requires explicit dependencies, e.g. the webapp samples, I've
> replaced
> the static ant file with and automatically generated one. In the case that
> some hand crafted ant script is needed, for example, to generate SDOs,
> then
> I have the ant generator just build build-dependency.xml which has the
> dependencies listed and which can then be included in the manually
> generated
> build.xml script.
> I haven't applied this change to all of the samples but it could be done.
> If
> we did have all of the dependencies explicitly described for all of the
> samples can we get rid of the "all" and "manifest" jars?
> Simon

I think its better if applications don't have to know or care about Tuscany
internals, that includes knowing all the different Tuscany module names and
all the dependencies they use. We haven't got this right yet so each time we
release our sample Ant builds break as the build.xml files get out of date -
this will be happening for any Ant builds our users have as well. The "all"
jar is an attempt to fix this, its a better way IMHO than having
applications specify every Tuscany module but theres a bit of work still to
do to make it work better for webapps. We've also talked before about
changing all the samples to be simple sca contributions that don't need any
mention of the Tuscany internals, this is something I think we really need
to do. Both of those things seem better to me than messing about trying to
generate build scripts.


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message