We are converting our seam
jboss tools-based projects into
maven projects.
My colleague did the initial research and conversion.
JBoss tools generates 3 projects when you create a seam project: web, ear, and
ejb projects. We preserved that structure and created 3 maven projects proj-web, proj-app, and proj-ear. He also created a proj-parent maven project to tie them together.
It seems to me that the task of the parent project, to tie all project together, is redundant to the task of the EAR project, proj-app, which creates an ear file containing the ejb jar and war files.
Furthermore, he designed all this on the command line and it's my job to figure out how to use it all in eclipse. The parent project set up does not play well in eclipse. I see no point to the parent project when "mvn install" on the app project builds the ear.
When does one really need a parent project? In this case isn't it redundant?