Vincent Massol wrote:
> Look. I think we are talking about the same thing. Except that in Maven
> case there is no need for a build.xml file at all. However, it is
> certainly needed for more complex builds (which is the reason for our
> maven.xml). In addition, Jelly let's us access easily the XML POM.
>
> [snip]
Exactly :-)
We attain the same goals from different perspectives, with different
approaches.
Since James tried to explain why he thinks using Jelly up front is
better, I explained why we think it's not necessarily needed.
I really don't /know/ what is the best, since we are both in new
territory, it's our best guess ;-)
But it seems we are really gaining from each other, even if sometimes
we are not aware of it. :-)
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
