Although I see the current structure of seam-gen much easier,
4 different projects is too complicated and confusing in my opinion,
Well, happy to see the ticket already exist, thanks :)
Seam-gen simplistic layout looks and feels simpler but has the downside that there is no clean seperation of jars (what is for compile, test and deploy?) which is rather essential when a tool (like eclipse or any other IDE) needs to provide proper code completion and navigation.
I don't claim the 4 project setup is easier, but at least things are cleanly separated.
Just information of why the structure is as is.
Note: this is exactly what things like Maven project structure dictates too...
Seamgen can also archive the jar/war/ear individually, so I think it's also ok,
but I agree regarding the clean separation and the need,
Thanks for the reply :-)