I've put some time into learning the Maven2 tool, and I find it absolutely wonderful. When I went to look into Seam a while ago, I found out that there was some major differences in Seam/Maven project structure and that there where no easy integration to use Maven2 to build, test, package Seam projects.
I wonder: Am I totally wrong here, is there really no problem using Seam/Maven2? If not, have there been any changes to this lately? Or is it planned?
Yeah good question. I came across the word Ivy - while browsing web for Seam related stuff - and it sounds like Maven2 sort of stuff. Does it provide different package structure and all? or I completely misunderstood the thing.
First, Seam does not have a "project structure". It operates in any standard Java EE packaging (WAR or EAR).
Now, seam-gen, on the other hand, is a project generator that comes with Seam that does produce a particular project structure. The structure that it produces, as you have observed, is not a standard Maven 2 layout. There are reasons for this, one of which is that it is optimized for quick redeployment whereas Maven 2 is pretty bad at doing anything quick.
You do not have to use seam-gen to use Seam, though I recommend that you start there so that you can play around with Seam without the hassle of figuring out how to set things up. You can also use the JBossTools plugin for Eclipse for the same purpose.
If you are interested in getting a Maven 2 project for Seam going, there is lots of discussion over at seamframework.org on this very topic. Seam does publish its artifacts to the JBoss Maven 2 repository and even provides a root POM which you can use to avoid having to identify all the dependencies. At this time, there is no official seam-gen equivalent that generates a Maven 2 project for Seam (though there are plans to do so). However, I'm sure there are plenty of places online today that you can find Maven 2 archetypes for Seam projects. [ October 08, 2008: Message edited by: Dan Allen ]