Heh. I've been following the maven dev list, and some of the re-
thinking done for 2.1 seems to clean things out substantially,
including resolving this whole issue of repeatability and making
things cleaner for stamping a build environment (sets of plugins,
etc.) I'm not saying this to suggest "stick with m2", but just to
validate that some news of the headaches are reaching the right
people, and things are being altered to address some of the worst of
this.
BTW, I've used the maven ant tasks for dependency stuff with great
success, using the dependency stuff to generate classpaths for ant
tasks. Might be the ticket for here, though I don't know if it will
build maven artifacts suitable for dropping on a repository auto-magi-
conveniently.
Christian.
On 31-Jan-08, at 11:11 , Howard Lewis Ship wrote:
It's quite possible to use Ant to build, but to generate Maven
artifacts. The dependencies are the good part of Maven, it's just the
build system layered on those dependencies that is atrocious.
On Jan 31, 2008 6:59 AM, Christian Edward Gruber
<[EMAIL PROTECTED]> wrote:
I'd like to second that, and at the very least, releasing maven
artifacts for those wanting to build T5 apps using M2 is critical.
This can be done regardless of whether T5 itself is using maven, but
it would be critical to easy use in most environments in which I have
worked or foresee working.
Christian.
On 31-Jan-08, at 09:56 , Mark W. Shead wrote:
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Howard M. Lewis Ship
Creator Apache Tapestry and Apache HiveMind
---------------------------------------------------------------------
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]
