deltaspike-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dan Allen <>
Subject Re: separate parent module - why not use the pom.xml from the main folder as parent?
Date Fri, 23 Dec 2011 23:02:17 GMT
I agree that it potentially puts some bumps in the road, but the benefit is
that you can import that parent into the IDE when it's adjacent to the
other modules. When it's above the modules, at least in Eclipse, it can't
be imported without having all the submodules as resources inside the
parent project. But perhaps that is just because Eclipse is goofy when it
comes to this project layout.


On Fri, Dec 23, 2011 at 17:58, Jakob Korherr <>wrote:

> Hi,
> I just checked the initial code in our git repo and found out that we
> have a separate parent module. Is there a reason why this module was
> created (I couldn't find a discussion about it)?
> IMO it is a lot better and easier to simply use the pom.xml in the
> main folder as the parent-pom for each module rather than having an
> own parent module. In MyFaces we have had quite a lot of problems with
> confused developers and confused tools (e.g. maven site generation),
> because we used the separate parent-module (e.g. in MyFaces ExtVal).
> That's the reason why we did this differently in CODI (I remember
> having a parent module in the very first draft of CODI too, but then
> changing it to the way it is now).
> This way we could also get rid of the relativePath declarations in the
> poms of our modules (e.g.
> <relativePath>../parent/pom.xml</relativePath>).
> Regards,
> Jakob
> --
> Jakob Korherr
> blog:
> twitter:
> work:

Dan Allen
Principal Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message