This is no longer true, Eclipse (m2e) supports both approaches nowadays. On 23 Dec 2011, at 23:02, Dan Allen wrote:
> 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. > > -Dan > > On Fri, Dec 23, 2011 at 17:58, Jakob Korherr <jakob.korh...@gmail.com>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>). >> >> WDYT? >> >> Regards, >> Jakob >> >> -- >> Jakob Korherr >> >> blog: http://www.jakobk.com >> twitter: http://twitter.com/jakobkorherr >> work: http://www.irian.at >> > > > > -- > Dan Allen > Principal Software Engineer, Red Hat | Author of Seam in Action > Registered Linux User #231597 > > http://google.com/profiles/dan.j.allen > http://mojavelinux.com > http://mojavelinux.com/seaminaction
