because it is much harder to use unless you already know how to use it (really steep learning curve)? because it forces you to work in
the maven way?
I think integrating with Ivy would be a better option.
Because Seam is built to work in Seam way and poses some restrictions on build system where maven is not flexible enough out-of-the-box :) and I mean Seam testing here - the rest works pretty easy.
As for what is a better solution... well, first of all, solution depends on a problem... and there is a difference between better and easier:)
I am not sure if IVY or the socalled SEAM way is better. I hope so. :-)
But maven2 is nowadays very popular and weit used everywhere. Our company uses maven2. If I build a project not using maven2, after I check into the repository, I will have problem.
I would like to say it should be a good way to add new features to the SEAM so that one can build the SEAM project with maven2. This will make SEAM more popular.
I'm using Seam with Flex front-end.
Seam way(seam-gen?) do not help me much here, since it is focused on JSF.
I'm using maven and I'm very happy with this combination :)
With you need a functional pom.xml with TestNG and Seam 2.1 and jboss embedded integrated, I can share the one that I have.
I hope they have maven 2 support soon.
Seam and it's dependencies are in the JBoss Maven repository . You can create a maven muti-module project that uses the maven eclipse plugin to generate WTP meta data which takes advantage of the hot deployment features in WTP.
Maven really makes upgrading seam versions easy,
I am currently using this on Eclipse Ganymede with JBoss tools 3.0.0.Alpha1 on Ubuntu 64 bit version.
I think it is the best of both worlds, WTP deployment with a great build system.