http://tapestryjava.blogspot.com/2007/11/maven-wont-get-fooled-again.html
After reading Howard's thoughts on using Maven for a large project, I'm concerned that Tapestry might drop Maven support entirely and I wanted to offer an end user perspective. As far as what is used to build T5 for the developers, I understand if they want to switch to something else. However, since most Java developers are going to be using Maven for something, I think it is vital to keep the capability of creating a T5 project from an archetype.
This lowers the barrier for people wanting to try it out. Doing away with this capability would increased the real (or at least perceived) complexity of "trying things out" for developers who are already using Maven for other things.
Just my two cents. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
